I am running tight-vnc 1.2.7 with the server on my RH8.0/Linux 2.4.20
Linux machine and the client on my WIn2k laptop which runs cygwin ssh.
I can tunnel vnc through ssh with local network addressing on the
192.168.1 subnet,
e.g., typing:
ssh 192.168.1.100 -l username -C -L 5902:192.168.1.100:5901
sets up a SSH connection and then I can open a vnc connection from the
win2k client using localhost:2 as the vnc server name
However, if I type the wan IP address 151.199.60.120 in place of
the local area 192.168.1 subnet address I get a ssh connection but can
no longer connect with the vnc win2k connect using the same
'localhost:2' server name.
Turning on debugging, I see the following
debug1: Connection to port 5902 forwarding to 151.199.60.120 port 5901
requested.
debug1: fd 9 setting TCP_NODELAY
debug1: fd 9 setting O_NONBLOCK
debug1: channel 2: new [direct-tcpip]
channel 2: open failed: connect failed: Connection refused
debug1: channel_free: channel 2: direct-tcpip: listening port 5902 for
151.199.60.120 port 5901, connect from 127.0.0.1 port 1079, nchannels 3
In both cases, both the Linux and Win2k machines sit behind a linksys
router with port forwarding turned on for port 22.
The only difference seems to be that in one case I use local LAN
addressing with all traffic staying internal to the LAN while in the
other case I use the WAN IP address with port forwarding. Also, note
that the SSH and port-forwarding itself seem to work right.
Note the debug output for the successful LAN connection is by
contrast:
debug1: Connection to port 5902 forwarding to 192.168.1.145 port 5901
requested.
debug1: fd 9 setting TCP_NODELAY
debug1: fd 9 setting O_NONBLOCK
debug1: channel 2: new [direct-tcpip]
debug1: channel 2: open confirm rwindow 131072 rmax 32768
I have tried starting 'vncserver' both with and without '-localhost'.
Any thoughts on what might be going wrong here?
Thanks,
Jeff
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
