> Second thought. WinVNC must bind to a particular adapter when it starts.
> If it binds to your local 192.168.x.x adapter, it will be invisible to the
> outside world. Since 192.168.x.x is unroutable (and since the server is
> not on your externally visible address), external connections can't get to
> it. I think I had to deal with this. Can't remember if it was a registry
> setting or if I had to set my external adapter's TCP/IP protocol to "be
the
> default protocol" under the Windows Network Settings. If WinVNC binds to
> the external adapter, then external connections will work, and internal
> connections will work as long as you use the external address. I don't
> know if WinVNC can be built to bind ports on all available adapters
> (requires separate connection listening for each adapter)
WinVNC binds to INADDR_ANY, or to INADDR_LOOPBACK, depending upon the
LoopbackOnly registry setting. So either WinVNC will only accept
connections from the local machine (suitable for SSH tunnelling) or it will
accept connections from any NIC.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
