tomtzigt "at" suscom-maine.net
Tue Dec 13 02:55:02 2005
So, if I am successful in connecting to the VNC server when I am inside the
LAN, AND I have port forwarding set to forward to the same IP address that I
am using when successfully connecting to the VNC server, AND I am seeing the
router forward the proper port when connecting from the WAN but I am still
seeing a vnc error: "unable to connect to host: Connection timed out
(10060)" what is the next step to see what might be misconfigured?
From: James Weatherall [mailto:jnw "at" realvnc.com]
Sent: Monday, December 12, 2005 1:52 PM
Cc: vnc-list "at" realvnc.com
Subject: Re: Trouble connecting
No. If a computer receives a TCPv4 connection request for a port on
which there is nothing accepting connections, it will respond with a
"Connection refused" message. "Connection timed out" means that
literally no response whatsoever was received from the server IP address.
Please see the tips at http://www.realvnc.com/portforward.html,
particularly the net-test link, which can be used from your VNC server
computer to determine whether your server is in fact contactable.
Wez @ RealVNC Ltd.
> I am confused. The computer doesn't respond does it? Some software that is
> listening to that port would respond, not? And that should presumably be
> VNC server which is running in a process.
> Whatever it is, I need more than that to get unstuck. The IP address of
> machine that is running the VNC server is 192.168.1.10. That address works
> when on the inside using vnc viewer. It is also programmed on the
> The port numbers are correct, the IP forwarding is correct. Other services
> are working, but not VNC. So I am looking for something that can tell me
> where that vnc packets are getting lost.
> All help is appreciated.
> -----Original Message-----
> From: James Weatherall [mailto:jnw "at" realvnc.com]
> Sent: Monday, December 12, 2005 6:15 AM
> To: 'tomtzigt'; vnc-list "at" realvnc.com
> Subject: RE: Trouble connecting
> Error 10060 does NOT mean that no process is listening to the request. It
> means that no *computer* responded to the request. This is most commonly
> because of firewall configuration or because the IP address that you are
> using is wrong.
> Wez @ RealVNC Ltd.
>>From: vnc-list-admin "at" realvnc.com
>>[mailto:vnc-list-admin "at" realvnc.com] On Behalf Of tomtzigt
>>Sent: 11 December 2005 13:57
>>To: vnc-list "at" realvnc.com
>>Subject: Trouble connecting
>>I am stuck..
>>I installed the latest VNC server on Fedora Core 2 and client
>>on Windows XP.
>>When I am on the inside of the network, I can connect to a
>>process, but when I am on the WAN I can't. The VNC Viewer
>>error I get back
>>is: "unable to connect to host: Connection timed out
>>(10060)", which after
>>reading this forum I interpret to mean that no process is
>>listening to the
>>request. I've painstakingly sifting through all the messages
>>from the router
>>and it successfully forwards the VNC TCP request to the
>>machine on which VNC
>>is running, but I can't get a VNC session going from the WAN
>>have any good ideas how further to debug this problem?
>>Sat, 2005-12-10 20:28:05 - TCP packet - Source: xxx -
>>Destination: xxx -
>>[Service access request successful Src 1164 Dst 5901 from WAN]
>>And VNC server is running:
>>[tomtzigt "at" Athena tomtzigt]$ ps -aux | grep vnc
>>tomtzigt 4025 0.9 2.7 17752 14276 pts/3 S Dec10 10:25 Xvnc :1
>>-desktop head-node -httpd /usr/share/vnc/classes -auth
>>/home/tomtzigt/.Xauthority -geometry 1400x1100 -depth 16
>>-rfbauth /home/tomtzigt/.vnc/passwd -rfbport 5901 -pn
>>Looking forward to get unstuck.
>>VNC-List mailing list
>>VNC-List "at" realvnc.com
>>To remove yourself from the list visit: