One Client Sys, Two Server Sys, Inconsistent Results
Ronald W. Heiby
heiby_vnc "at" falkor.chi.il.us
Fri Jul 12 07:31:01 2002
-----BEGIN PGP SIGNED MESSAGE-----
I've spent quite a few hours tracking things down, and finally found a
difference between my home and work configuration.
At work, the name by which I established the SSH connection is
included in the /etc/hosts file as a synonym for 127.0.0.1. At home,
this was not done. When SSH attempted to open the tunnel port, it
attempted to use the name by which it established the original
connection, which caused it to attempt to open port 5901 on the
router. Since my router does not have port 5901 forwarded, the tunnel
connection never completed.
So, problem solved, right? Well, sort of. Although my VNC connection
through the SSH tunnel is working just fine at home and at work, when
I actually try to pump a bunch of data through that link when going
through the Linksys BEFSR11 router, as when I bring up a complex web
page in the VNC display, the SSH connection that is hosting the tunnel
VNC session dies.
I have seen this several times now, when going through the Linksys. I
have not seen it when I connect using the 192.168.xx.xx local LAN
address to reach the same server at home. I have not seen it when I
connect to my office machine through another firm's router.
Any ideas on what's going on here? Is it just a FUBAR router? Or, is
there some kind of configuration option I might try? I think I'm using
default options on my Win2K VNC client. (Hexfile, Allow CopyRect
encoding, Emulate 3 Buttons, and no other items checked.)
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.8
Comment: The last PGP with full source disclosure.
-----END PGP SIGNATURE-----