Hal Vaughan napisal(a): [Charset utf-8 unsupported, skipping...] > ports closed unless I'm working with a client). B On his system he's running > vncserver and it is using display :1, so he uses this command line: > > vncconfig -display :1 -connect myname.dyndns.org > > And we don't get any connection. When I run the same line from inside my > LAN, > so it connects by going through dyndns.org, it works. B When my friend does > it [...] > to send the connection through port 80. B If he tries to read a web page on > my > address, I see it on my firewall logs, but when he tries this (trying to > connect to my vncviewer), I see nothing in the firewall logs.
And what is the actual IP address that "hides" behind myname.dyndns.org? Are you *absolutely sure* that DNS query on myname.dyndns.org returns your real, public IP address that can be reached from the Internet? Isn't it possible that the DynDNS client is broadcasting your *internal* LAN IP address to the DynDNS server? That address is of course not reachable from outside. The absence of entries in firewall logs could indicate that your friend is trying to connect to a wrong address. Have your friend type "ping myname.dyndns.org" on his machine and note the IP address that is displayed along with the hostname. Then check whether it's your actual IP address. Regards, Jaroslaw Rafa [EMAIL PROTECTED] -- Spam, wirusy, spyware... masz do6f? Jest alternatywa! http://www.firefox.pl/ --- http://www.thunderbird.pl/ Szybciej. #atwiej. Bezpieczniej. Internet tak jak lubisz. _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
