On Friday 02 March 2007 06:48, Chris Swain wrote: > Here's the problem: I can successfully access my Desktop PC via VNC when I > connect from within my LAN (e.g. connecting via an internal IP address - > 192.168.1.104 works). However I cannot access my Desktop PC when I try to > connect from outside the LAN (e.g. connecting via an external IP address > -71.105.67.xxx returns a "Failed to connect to server" message).
Which means that your router and/or firewall configuration blocks the connection. > Here are some details about my configuration: > > 1. my ISP, Verizon, does not block VNC traffic. I've called their tech > support multiple times to confirm this and run tests. > > 2. My modem/router is an ActionTec GT704-WG, version 3. I've talked to > their tech support multiple times as well to confirm that VNC should work > and to run tests. > > 3. Port forwarding is working properly on the router. This is confirmed > when I connect via an internal IP address No, it's not. Port forwarding on your LAN works (i.e. from 192.168.1.XXX to 192.168.1.YYY). This is the default setting on most/any router. Port forwarding through your router from WAN most likely does not work. Incidentally, this is what 'port forwarding' means these days. What do you see when you telnet using a WAN machine to your VNC server IP address and port? > 4. Turning off the Windows firewall does not fix the problem Good. This means that the attempt to connect fails before it even reaches your WinXP box. If you are using the correct IP address, then the router stops it. > 5. I am running Windows XP Media Center Edition Version 2002, Service > Pack 2 on the Desktop PC > > 6. Desktop PC has a static internal IP address Good. Is the external IP address statically or dynamically allocated by your ISP? > 7. Remote access is enabled on the router I am sorry - not sure what you mean here. Are you saying that you can access your router's admin GUI from the WAN to administer it? I hope that you have set an insanely long and difficult password. > 8. NETSTAT -AN shows that VNC ports (5800 and 5900) are listening > properly Good, in all likelihood the VNC server is correctly set. > 9. This problem disappeared a week ago meaning I could access via an > external IP address for a few days but then the problem returned (!?). Hmm. If that is so, then something must have changed. If you did not update the firmware or changed the settings on your router, have you checked that your external IP address is the same? Do you have a fixed internet IP address, or a dynamically allocated one? Google for "what is my IP address". > 10. Before installing the ActionTec modem router I had the same problem > with a Westell 6100 modem and Belkin router. Before the Westell 6100 I had > an old Westell DSL modem that allowed VNC traffic fine. My guess from your excellently detailed symptoms above is that you will need to set up port forwarding *correctly* at your router and use the appropriate IP address. Check the FAQs on the Real VNC website. Guidance for connections through a NAT router are discussed there and a link to a website for setting up port forwarding for many different type of routers is provided. HTH. PS. If you are using the free VNC server edition consider tunnelling the VNC connection through a SSH tunnel for security purposes (CopSSH and PuTTY is probably the easiest to set up). In either case, see if you can allow port forwarding connections at your router from your client's IP address only, not from the www. Ditto at your server WinXP software firewall. -- Regards, Mick [demime 1.01d removed an attachment of type application/pgp-signature] _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
