Routing or VNC Problem?

[Matthew.van.Eerde@hbinc.com]

Sounds like a firewall problem, if port 80 gets through and 5900 doesn't.
Maybe you're blocking all but a few well-known ports.  Try a traceroute to
see what routers are forwarding from 192.168.0.x to 192.168.1.x, and check
the firewalls along the path.

-----Original Message-----
From: Mike Morrell [mailto:mike "at" themorrells.org]
Sent: Monday, November 05, 2001 13:46
To: vnc-list "at" uk.research.att.com
Subject: Routing or VNC Problem?


   We have VNC running on several windows based computers for remote admin.
Recently we  installed Redhat 7.1 on one of them.  Computers in the same
subnet, 192.168.0.x can access this machine with  the VNC client software or
web interface with no problem.  Computer in our other subnet 192.168.1.x can
only access the machine using the web client.  The VNC client software, or
even telneting to that ip and port, gets a connection refused.  I have
checked xinetd and it is not specifically blocking 192.168.1.x subnet and
the /var/log/messages and /var/log/secure logs show no errors.  The VNC log
does not even show an attempt to connect.
   Is there some routing trick I need to apply here?  We can ping this
computer from the other subnet with no problem and the web interface for VNC
 works fine.  Does inetd/xinetd block connections from other subnets by
default?

 Thanks,

 Mike
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------