Mick, Thanks for your time, but I just found the problem. 2Wire lists all the devices that were ever connected to it by name, not by IP address. I was pointing port 5902 to a computer that has long been deceased and was replaced by a new machine that inherited its name. So 2Wire assigned a new IP to the newcommer but still maintains both identical names in its list of networked devices. I feel so dumb. Thanks again. Jean-Louis
On 3/2/07, Mick <[EMAIL PROTECTED]> wrote: > > On Friday 02 March 2007 21:05, Jean-Louis Dehoux wrote: > > Here is the setup: > > > > 1 Laptop with XP Home with AVG Firewall > > 1 Desktop with XP Pro with Windows Firewall > > 1 2Wire HomePortal Modem/Router > > > > I downloaded and installed RealVNC 4.1.2 on both machines and set the > > connection port to 5901 on the laptop and 5902 on the desktop. > > > > On both machines, I opened their respective port in their firewalls and > > allowed winvnc.exe to communicate with the outside world. > > > > On the router, I forwarded incoming traffic on port 5901 to the laptop > and > > port 5902 to the desktop. > > > > Using the VNC viewer, the machines see each other when using the local > IPs > > such as 192.168.0.22:5901 from the desktop to view the laptop and > > 192.168.0.23:5902 from the laptop to view the desktop. > > > > Here where it gets crazy: > > > > Assume the public IP is 70.70.70.70 (as I would read it from a site such > as > > WhatIsMyIP.com) > > > > I can view the laptop from the desktop using 70.70.70.70:5901 > > But not the other way around. Aaargh... > > > > Any idea of what I am doing wrong??? > > Have you temporarily tried switching off the desktop WinXP firewall? Have > you > tried to telnet from the laptop to the desktop, port 5092? What are you > getting? > > -- > Regards, > Mick _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
