Test your own VNC
It can be a royal pain in the behind to debug VNC running across a firewall/router setup while you're *behind* that firewall (eg on the VNC server itself). With some firewall/routers (like mine, a Belkin High-Speed Mode Wireless G), even if you have the firewall's port-forwarding for VNC setup correctly, you may not be able to connect a viewer to your server, even if you're using the "real world" external IP address that you just (tried to) enable. Trying it will result in the super-cryptic, not very helpful but darned popular error "Connection refused (10061)".
Fortunately, there's an easy solution. Simply go to gotomyvnc.com and it will launch a port scan on your IP to see if your router rules have been setup correctly. Kewl!
Fortunately, there's an easy solution. Simply go to gotomyvnc.com and it will launch a port scan on your IP to see if your router rules have been setup correctly. Kewl!
4 Comments:
what would it say if it works?0
By Anonymous, at 12:52 PM
It will list which ports/displays your pc is accepting connections.
By Anonymous, at 6:44 AM
A very helpfull information !
I didn't have any clue about this !
Best Regards to Informer !!!
By Anonymous, at 6:40 PM
Hello,
I'm using a VNC in WinXP wich has a server with linux and a route modem.
Instead of find the IP of modem, you script is finding my WinXP IP in my network. Is that correct? Cause I can't test VNC.
Thanks for your effort.
By Anonymous, at 6:26 AM
Post a Comment
<< Home