Hi Paresh, VNC Server by default listens on INADDR_ANY (i.e. all network interfaces). It sounds like the TCP stack of the computer on which you are running the server doesn't handle new network interfaces in the obvious way, so that existing INADDR_ANY services don't get to use them. The vendor of the operating system you're using may be able to provide a fix for the problem.
Regards, -- Wez @ RealVNC Ltd > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of PARESH MASANI > Sent: 11 June 2008 10:22 > To: vnc-list@realvnc.com > Subject: VNC server will not listen on interface that has > been added after VNC Service started > > Hi All, > > I found some issue with VNC Server after configuring new > interface. The VNC server does not listen on newly configured > interface and failed to connect this interface from other > machine. For an instance say computer is in LAN and its IP > address on that interface is 190.220.1.0. We can start VNC > server and will able to connect from any machine on LAN using > that IP address. Now say I connected my computer to another > LAN(or may be via VPN-wireless network interface). New IP > address will be generated say 190.220.1.1 via DHCP protocol. > If I try to connect to VNC server on new IP address > 190.220.1.1 then it is not working. I have to unplug the > older LAN connection to make VNC server to work for newly interface. > > Could you please tell me if anyone faced the same problem or > any one know the solution. > > > Regards, > Paresh > > > Meet people who discuss and share your passions. Go to > http://in.promos.yahoo.com/groups/bestofyahoo/ > _______________________________________________ > VNC-List mailing list > VNC-List@realvnc.com > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list > _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
