Routing or VNC Problem?
Mike Morrell
mike "at" themorrells.org
Mon, 05 Nov 2001 23:31:57 +0000
Yeah, tried this. It too gets connection refused. I just can figure out
why I can ping across the subnets and use the web interface with no problem
but then have trouble telnet'ing to the port and using the VNC client.
Maybe I will try them all again and make sure I did not miss something.
Mike
----- Original Message -----
From: "Glenn Mabbutt" <gmabbutt "at" quartetservice.com>
To: <vnc-list "at" uk.research.att.com>
Sent: Monday, November 05, 2001 3:45 PM
Subject: RE: Routing or VNC Problem?
> OK, so what happens if you try "telnet <IPtoConnectTo> 5901" from the
other
> subnet to the box you're trying to connect to?? (substitute 590x where x
is
> the display you're connecting to) You should see "RFB 3.3" and a bunch of
> other stuff.
>
> -----Original Message-----
> From: Mike Morrell [mailto:mike "at" themorrells.org]
> Sent: Monday, November 05, 2001 5:27 PM
> To: vnc-list "at" uk.research.att.com
> Subject: Re: Routing or VNC Problem?
>
>
> The two subnets are connected together by a VPN tunnel with all ports
> allowed. I had forgotten to mention that we do have other computers on
the
> same subnet but running VNC on windows and we can access them across
subnets
> with no problems.
>
>
> Mike
>
>
> ----- Original Message -----
> From: <Matthew.van.Eerde "at" hbinc.com>
> To: <vnc-list "at" uk.research.att.com>
> Sent: Monday, November 05, 2001 3:02 PM
> Subject: RE: Routing or VNC Problem?
>
>
> > 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
> > ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------
---------------------------------------------------------------------
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
---------------------------------------------------------------------