jnw "at" realvnc.com
Wed Jan 26 10:35:01 2005
If the Windows machine is running Windows XP SP2, you'll need to disable its
firewall, or make VNC Server an Exception to it (VNC Enterprise Edition
4.1.3 will do this for you, if you wish).
Are you sure that you have the correct address for your LAN's firewall? Is
it pingable? Error 10060 means that there was absolutely no response at all
from the target machine, which is consistent with a firewall being in place,
with the computer not existing, or with the address being wrong (and
pointing to a machine that doesn't exist...)
Wez @ RealVNC Ltd.
> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com
> [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Kevin Duffy
> Sent: 26 January 2005 03:00
> To: vnc-list "at" realvnc.com
> Subject: newbie question
> I am attempting the connect to a Windows machine running the
> VNC Enterprise
> To do this I did the following:
> On the firewall of the LAN for the VNC Enterprise server
> forward port 5900
> to the server machine.
> On the remote machine download VNC Enterprise Viewer.
> Run the viewer and enter the IP address of the firewall (ie
> xxx.xxx.xxx.97:0) colon zero because we are connecting to a
> Windows machine.
> This should work. True?
> I get Attempting to connect to host for several seconds and then
> Error unable to connect to host:Connection timed out (10060)
> Your assistance to greatly appreciated.
> Kevin Duffy
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: