Thanks for doing testing. Could you please make sure that the network topology you have tested and my network's topology(attached file) is same. Please check all the three cases and Please let me know if real VNC will work in all cases or not.
Thanks, Paresh On 6/17/08, Seak, Teng-Fong <[EMAIL PROTECTED] <[EMAIL PROTECTED]>> wrote: > > OK, I think I guess what network topology you've got. You're > probably using a Wifi router which also has ethernet ports. And your > PC is connected to the router via wireless and wired connection. > (Digression: you're not supposed to do so since you've created a loop > in your network. Anyway) > > I've tried the same test, but I don't have your problem. Indeed, > my PC is first connected with cable to my router. VNC test ok from > another PC. Then I connect it through Wifi WITHOUT unplugging the > cable. VNC test using Wifi's IP address is also OK. > > On Thu, Jun 12, 2008 at 8:25 AM, paresh masani <[EMAIL PROTECTED]> > wrote: > >>> Do you mean you have two network interfaces? > > Yes, wired and wireless. In this case I tried to take VNC from other > machine > > and it is working fine for wired interface but not for wireless. For > > wireless, using TCPView i could see that other machine's request came but > > the status stays "SYN_RCVD" forever and at last it says "connection timed > > out". > > > >>>And when you gave the example of 190.220.1.0, I hope it's really > > Its not real address. i gave it just for an example. > > > > Thanks, > > Paresh > > > > On 6/11/08, Seak, Teng-Fong <[EMAIL PROTECTED]<[EMAIL PROTECTED]>> > wrote: > >> > >> Do you mean you have two network interfaces? Because if you've > >> just got one interface, I can't see how you could "unplug the older > >> LAN connection". > >> > >> And when you gave the example of 190.220.1.0, I hope it's really > >> an example because x.x.x.0 is normally a network address and can't be > >> used by any host. > >> > >> And lastly, have you tried to ping that new IP address to make > >> sure the new IP is reachable? > >> > >> On Wed, Jun 11, 2008 at 11:22 AM, PARESH MASANI > >> <[EMAIL PROTECTED]> wrote: > >> > 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. > >> _______________________________________________ > >> 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 > _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
