Winsock Error Codes - Brought to you by Winsock-Error.com

10060 "Connection timed out."

WSAETIMEDOUT (Winsock error number: 10060)

Microsoft say this about Winsock error 10060 - WSAETIMEDOUT:

A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.

Full details of Winsock TCP error 10060 - WSAETIMEDOUT:

Berkeley description: A connect or send request failed because the connected party did not properly respond after a period of time. (The timeout period is dependent on the communication protocol.)

WinSock description: Same as Berkeley, but less. This error is relevant to, but not to or sendto() as it is in Berkeley Sockets.

User suggestions: Check the obvious first: check that the destination address is a valid IP address. If you used a hostname, did it resolve to the correct address? If the hostname resolution uses a local host table, it's possible you resolved to an obsolete address. Can you ping that hostname?

Do you have a router configured? Is the router up and running (check by pinging it, and then ping an address on the other side of it)? Try a traceroute to the destination address to check that all the routers are functioning.

Check your subnet mask. If you don't have the proper subnet mask, your network system may treat a local address as a remote address (so it forwards addresses on the local subnet to the router, rather than broadcasting an ARP request locally), or visa versa.

   
This page is designed to help you to understand Winsock TCP error 10060. It will not necessarily mean you can instantly fix issues when your computer tells you that Winsock is having problems with code 10060, rather it will give you the necessary background information to help solve the matter.

Programming declarations for 10060 (WSAETIMEDOUT):

C#
long WSAETIMEDOUT = 10060 ;

VB.net
Dim WSAETIMEDOUT As Long = 10060

VB6
Dim WSAETIMEDOUT As Long
WSAETIMEDOUT = 10060