not listening on added interface
peyton+realvnc "at" freeshell.org
Wed Jan 4 22:02:00 2006
This is a somewhat technical question.
We've been using VNC for some time now at my office, and we think
we've recently discovered a bug. I'd like to know if anyone else has
noticed this behavior, whether anyone can reproduce it, and whether
anyone knows if there's a fix.
When a new network interface is configured in Windows after the VNC
server has already been started, it appears the VNC server will not
listen for connections on that interface.
Example: let's say you're plugged in via ethernet to your local area
network and your IP is 192.168.0.1 on that interface. You start VNC
server and you're able to connect to it from another machine using
that IP address. Now try associating with an access point via your
wireless network interface (alternately, plug in another ethernet
connection if that's possible). You get another IP address via DHCP
-- let's say 192.168.0.2. Trying to connect to the VNC server on that
interface's IP address does not work. If you disconnect the first
interface (unplug the ethernet cord) and Windows realizes it's gone,
discards the IP, etc, try connecting to the second interface again
(192.168.0.2) -- it works.
Again, has anyone noticed this behavior or can you reproduce it?
Thanks in advance!