Mailing List Archive: VNC: list

connection timed out (10060)

Index | Next | Previous | View Threaded

samplb at hk1

Nov 4, 2005, 11:05 PM

Post #1 of 7 (14341 views)
Permalink

connection timed out (10060)

Hi, with correct server IP address; any suggestion or experience in

seeing 'unable to connect to host: connection timed out (10060)' message ?

It's all W2K environment at both server and client.

Thanks

Best Regards,
Paul Sam
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

jerry at westrick

Nov 5, 2005, 1:15 AM

Post #2 of 7 (14207 views)
Permalink

Re: connection timed out (10060) [In reply to]

On Saturday 05 November 2005 08:05, Paul LB Sam wrote:
> Hi, with correct server IP address; any suggestion or experience in
>
> seeing 'unable to connect to host: connection timed out (10060)' message ?
>
> It's all W2K environment at both server and client.
>
> Thanks
>
> Best Regards,
> Paul Sam

Hi Paul the error msg means that the server is not running on the remote
machine. What it really happens is that the TCP/IP connection could not be
made.

The best way to debug this is using telnet in a dosbox.
Basically it goes like this:

telnet ipaddress portno

This tells telnet to open a tcp/ip connection to ipaddress on port portno.
You can have multiple VNCs running, so the portno VNC uses is quite flexible.
THe default port, (which I'm sure you didn't change did you?) is 5900.

When you run telnet you should get a line with "RFB 3" in it. If you do then
VNC server is running correctly AND you can build a tcp/ip connection to it.

Now if Telnet gives you an error, then you got 2 possibilities:
1) the server is not running on the correct port.
2) the tcp/ip connection cannot be established.

On the same machine as the vnc server run:
telnet 127.0.0.1 5900

If you get the "RFB 3" msg, the server is running on the correct port.
proceed to firewalls below:

If not your server is not running on the correct port.
1) look to see if vncserver is running at all.
if it is not, that is your problem.
if it is, the parameters are messed up, and it not listening to port 5900

Firewalls (Below):

(Sorry for the little joke there, just couldn't help myself).
Okay, Wher are we?
- Server is running on correct port on machine "S",
- but Client on Machine "C" cannot connect.

Here I cannot give you a step-by-step...
but it is your firewall, Internet Security settings, or network settings.

Come back after you've done above...
We'll help you out wiht the next step...

Jerry
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

jnw at realvnc

Nov 5, 2005, 7:58 AM

Post #3 of 7 (14224 views)
Permalink

RE: connection timed out (10060) [In reply to]

Jerry & Paul,

The error message in question does *NOT* mean that the server isn't running,
but that the IP address you specified is not responding *at all*, indicating
that there's a firewall in place, or it's the wrong IP address, etc. If the
server wasn't running, you'd instead get "Connection refused".

Cheers,

Wez @ RealVNC Ltd.

> -----Original Message-----
> From: vnc-list-admin [at] realvnc
> [mailto:vnc-list-admin [at] realvnc] On Behalf Of Jerry Westrick
> Sent: 05 November 2005 09:16
> To: vnc-list [at] realvnc
> Subject: Re: connection timed out (10060)
>
> On Saturday 05 November 2005 08:05, Paul LB Sam wrote:
> > Hi, with correct server IP address; any suggestion or experience in
> >
> > seeing 'unable to connect to host: connection timed out
> (10060)' message ?
> >
> > It's all W2K environment at both server and client.
> >
> > Thanks
> >
> > Best Regards,
> > Paul Sam
>
> Hi Paul the error msg means that the server is not running on
> the remote
> machine. What it really happens is that the TCP/IP
> connection could not be
> made.
>
> The best way to debug this is using telnet in a dosbox.
> Basically it goes like this:
>
> telnet ipaddress portno
>
> This tells telnet to open a tcp/ip connection to ipaddress on
> port portno.
> You can have multiple VNCs running, so the portno VNC uses is
> quite flexible.
> THe default port, (which I'm sure you didn't change did you?) is 5900.
>
> When you run telnet you should get a line with "RFB 3" in it.
> If you do then
> VNC server is running correctly AND you can build a tcp/ip
> connection to it.
>
> Now if Telnet gives you an error, then you got 2 possibilities:
> 1) the server is not running on the correct port.
> 2) the tcp/ip connection cannot be established.
>
> On the same machine as the vnc server run:
> telnet 127.0.0.1 5900
>
> If you get the "RFB 3" msg, the server is running on the
> correct port.
> proceed to firewalls below:
>
> If not your server is not running on the correct port.
> 1) look to see if vncserver is running at all.
> if it is not, that is your problem.
> if it is, the parameters are messed up, and it not listening
> to port 5900
>
>
>
> Firewalls (Below):
>
> (Sorry for the little joke there, just couldn't help myself).
> Okay, Wher are we?
> - Server is running on correct port on machine "S",
> - but Client on Machine "C" cannot connect.
>
> Here I cannot give you a step-by-step...
> but it is your firewall, Internet Security settings, or
> network settings.
>
> Come back after you've done above...
> We'll help you out wiht the next step...
>
> Jerry
> _______________________________________________
> VNC-List mailing list
> VNC-List [at] realvnc
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

joelrob at us

Nov 7, 2005, 7:59 AM

Post #4 of 7 (14232 views)
Permalink

Re: connection timed out (10060) [In reply to]

I get this error when I mistakenly indicate the wrong port on the client
machine. I have two different servers I connect to, each on it's own port
so I can have the sessions up simultaneously. Whenever I forget to change
the port at the login screen, I get this same error.

Thank you,

Joel J Roberts
ODCS Network Specialist

"Part of the facts is understanding we have a problem, and part of the
facts is what you're going to do about it." ?George W. Bush

Paul LB Sam <samplb [at] hk1>
Sent by: vnc-list-admin [at] realvnc
11/05/2005 12:05 AM

To
vnc-list [at] realvnc
cc

Subject
connection timed out (10060)

Hi, with correct server IP address; any suggestion or experience in

seeing 'unable to connect to host: connection timed out (10060)' message ?

It's all W2K environment at both server and client.

Thanks

Best Regards,
Paul Sam
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

edranem at dranem

Aug 31, 2008, 8:13 PM

Post #5 of 7 (10129 views)
Permalink

Re: Connection timed out (10060) [In reply to]

what antivirus are you using?
some antivirus will disable remote software
either the software isn't listenig;
there is a firewall in place
the firewall isn't set to allow it through
or the AV is stopping it

steve

Maggie Owens wrote:
> I read a number of messages on this forum about this particular message,
> but none of them seem to address my particular problem.
>
> Both the client and server are running Windows XP. From this client, I can
> connect to a number of machines in my office, but one in particular is not
> working. I know the IP address is correct because I can use Remote Desktop
> to connect to it.
>
> Other than setting a password, I left all the defaults in place, which is
> how it appears to be on the other machines (I am not the one who installed
> it on the other machines).
>
> The Windows Firewall is turned off, and no other firewall is installed on
> the machine.
>
> If I try to telnet to the machine using the VNC default port (I saw
> something about this in one of the messages, but not what response I
> should receive), I get the message "Could not open connection to the host,
> on port 5900: Connect failed" This must have something to do with the
> problem, as I am able to telnet to another one of the machines on which
> VNC is working.
>
> Any suggestions would be appreciated.
> _______________________________________________
> VNC-List mailing list
> VNC-List [at] realvnc
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

mmowens at panix

Sep 2, 2008, 11:34 AM

Post #6 of 7 (10090 views)
Permalink

Re: Connection timed out (10060) [In reply to]

Thanks for your answer, but to quote Christopher Eccleston in Doctor Who,
"Look at me, I'm stupid!" I typed in the wrong IP address. It is working
fine now.

> what antivirus are you using?
> some antivirus will disable remote software
> either the software isn't listenig;
> there is a firewall in place
> the firewall isn't set to allow it through
> or the AV is stopping it
>
> steve
>
>
> Maggie Owens wrote:
>> I read a number of messages on this forum about this particular message,
>> but none of them seem to address my particular problem.
>>
>> Both the client and server are running Windows XP. From this client, I
>> can
>> connect to a number of machines in my office, but one in particular is
>> not
>> working. I know the IP address is correct because I can use Remote
>> Desktop
>> to connect to it.
>>
>> Other than setting a password, I left all the defaults in place, which
>> is
>> how it appears to be on the other machines (I am not the one who
>> installed
>> it on the other machines).
>>
>> The Windows Firewall is turned off, and no other firewall is installed
>> on
>> the machine.
>>
>> If I try to telnet to the machine using the VNC default port (I saw
>> something about this in one of the messages, but not what response I
>> should receive), I get the message "Could not open connection to the
>> host,
>> on port 5900: Connect failed" This must have something to do with the
>> problem, as I am able to telnet to another one of the machines on which
>> VNC is working.
>>
>> Any suggestions would be appreciated.
>> _______________________________________________
>> VNC-List mailing list
>> VNC-List [at] realvnc
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>
>>
>
>
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

jpm at cfl

Sep 2, 2008, 12:16 PM

Post #7 of 7 (10099 views)
Permalink

Re: Connection timed out (10060) [In reply to]

in my situation, the ip address is correct... i do in fact connect to the
remote machine. it's just that only a title bar is displayed, no window of
the remote desktop is displayed. i can right-click on the title bar and
check the connection info which indicates that the connection is functioning
normally. but obviously, something isn't normal.

john
----- Original Message -----
From: "Maggie Owens" <mmowens [at] panix>
To: "Stephen Menard" <edranem [at] dranem>
Cc: <vnc-list [at] realvnc>
Sent: Tuesday, September 02, 2008 2:34 PM
Subject: Re: Connection timed out (10060)

> Thanks for your answer, but to quote Christopher Eccleston in Doctor Who,
> "Look at me, I'm stupid!" I typed in the wrong IP address. It is working
> fine now.
>
>
>> what antivirus are you using?
>> some antivirus will disable remote software
>> either the software isn't listenig;
>> there is a firewall in place
>> the firewall isn't set to allow it through
>> or the AV is stopping it
>>
>> steve
>>
>>
>> Maggie Owens wrote:
>>> I read a number of messages on this forum about this particular message,
>>> but none of them seem to address my particular problem.
>>>
>>> Both the client and server are running Windows XP. From this client, I
>>> can
>>> connect to a number of machines in my office, but one in particular is
>>> not
>>> working. I know the IP address is correct because I can use Remote
>>> Desktop
>>> to connect to it.
>>>
>>> Other than setting a password, I left all the defaults in place, which
>>> is
>>> how it appears to be on the other machines (I am not the one who
>>> installed
>>> it on the other machines).
>>>
>>> The Windows Firewall is turned off, and no other firewall is installed
>>> on
>>> the machine.
>>>
>>> If I try to telnet to the machine using the VNC default port (I saw
>>> something about this in one of the messages, but not what response I
>>> should receive), I get the message "Could not open connection to the
>>> host,
>>> on port 5900: Connect failed" This must have something to do with the
>>> problem, as I am able to telnet to another one of the machines on which
>>> VNC is working.
>>>
>>> Any suggestions would be appreciated.
>>> _______________________________________________
>>> VNC-List mailing list
>>> VNC-List [at] realvnc
>>> To remove yourself from the list visit:
>>> http://www.realvnc.com/mailman/listinfo/vnc-list
>>>
>>>
>>
>>
> _______________________________________________
> VNC-List mailing list
> VNC-List [at] realvnc
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
>
_______________________________________________
VNC-List mailing list
VNC-List [at] realvnc
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com