Connection attempt failed with error 10060 proxifier

Network error codes

In the case of network errors (e.g. a connection to a proxy server fails) Proxifier outputs error code numbers. These are the standard Winsock error codes. This section contains the codes of network errors and their description.

WSAEACCES
(10013)
Permission denied.
An attempt was made to access a socket in a way forbidden by its access permissions.
An example is using a broadcast address for sendto without broadcast permission
being set using setsockopt(SO_BROADCAST).
Another possible reason for the WSAEACCES error is that when the bind function
is called (on Windows NT 4 SP4 or later), another application, service, or kernel
mode driver is bound to the same address with exclusive access. Such exclusive
access is a new feature of Windows NT 4 SP4 and later, and is implemented by
using the SO_EXCLUSIVEADDRUSE option.

WSAEADDRINUSE
(10048)
Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port)
is permitted. This error occurs if an application attempts to bind a socket
to an IP address/port that has already been used for an existing socket, or
a socket that was not closed properly, or one that is still in the process of
closing. For server applications that need to bind multiple sockets to the same
port number, consider using setsockopt(SO_REUSEADDR). Client applications usually
need not call bind at all—connect chooses an unused port automatically.
When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE
error could be delayed until the specific address is committed. This could happen
with a call to another function later, including connect, listen, WSAConnect,
or WSAJoinLeaf.

WSAEADDRNOTAVAIL
(10049)
Cannot assign requested address.
The requested address is not valid in its context. This normally results from
an attempt to bind to an address that is not valid for the local machine. This
can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo
when the remote address or port is not valid for a remote machine (for example,
address or port 0).

WSAEAFNOSUPPORT
(10047)
Address family not supported by protocol family.
An address incompatible with the requested protocol was used. All sockets are
created with an associated address family (that is, AF_INET for Internet Protocols)
and a generic protocol type (that is, SOCK_STREAM). This error is returned if
an incorrect protocol is explicitly requested in the socket call, or if an address
of the wrong family is used for a socket, for example, in sendto.

WSAEALREADY
(10037)
Operation already in progress.
An operation was attempted on a nonblocking socket with an operation already
in progress—that is, calling connect a second time on a nonblocking socket
that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY)
that has already been canceled or completed.

WSAECONNABORTED
(10053)
Software caused connection abort.
An established connection was aborted by the software in your host machine,
possibly due to a data transmission time-out or protocol error.

WSAECONNREFUSED
(10061)
Connection refused.
No connection could be made because the target machine actively refused it.
This usually results from trying to connect to a service that is inactive on
the foreign host—that is, one with no server application running.

WSAECONNRESET
(10054)
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally
results if the peer application on the remote host is suddenly stopped, the
host is rebooted, or the remote host uses a hard close (see setsockopt for more
information on the SO_LINGER option on the remote socket.) This error may also
result if a connection was broken due to keep-alive activity detecting a failure
while one or more operations are in progress. Operations that were in progress
fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

WSAEDESTADDRREQ
(10039)
Destination address required.
A required address was omitted from an operation on a socket. For example, this
error is returned if sendto is called with the remote address of ADDR_ANY.

WSAEFAULT
(10014)
Bad address.
The system detected an invalid pointer address in attempting to use a pointer
argument of a call. This error occurs if an application passes an invalid pointer
value, or if the length of the buffer is too small. For instance, if the length
of an argument, which is a SOCKADDR structure, is smaller than the sizeof(SOCKADDR).

WSAEHOSTDOWN
(10064)
Host is down.
A socket operation failed because the destination host is down. A socket operation
encountered a dead host. Networking activity on the local host has not been
initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.

WSAEHOSTUNREACH
(10065)
No route to host.
A socket operation was attempted to an unreachable host. See WSAENETUNREACH.

WSAEINPROGRESS
(10036)
Operation now in progress.
A blocking operation is currently executing. Windows Sockets only allows a single
blocking operation—per- task or thread—to be outstanding, and if
any other function call is made (whether or not it references that or any other
socket) the function fails with the WSAEINPROGRESS error.

WSAEINTR
(10004)
Interrupted function call.
A blocking operation was interrupted by a call to WSACancelBlockingCall.

WSAEINVAL
(10022)
Invalid argument.
Some invalid argument was supplied (for example, specifying an invalid level
to the setsockopt function). In some instances, it also refers to the current
state of the socket—for instance, calling accept on a socket that is not
listening.

WSAEISCONN
(10056)
Socket is already connected.
A connect request was made on an already-connected socket. Some implementations
also return this error if sendto is called on a connected SOCK_DGRAM socket
(for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other
implementations treat this as a legal occurrence.

WSAEMFILE
(10024)
Too many open files.
Too many open sockets. Each implementation may have a maximum number of socket
handles available, either globally, per process, or per thread.

WSAEMSGSIZE
(10040)
Message too long.
A message sent on a datagram socket was larger than the internal message buffer
or some other network limit, or the buffer used to receive a datagram was smaller
than the datagram itself.

WSAENETDOWN
(10050)
Network is down.
A socket operation encountered a dead network. This could indicate a serious
failure of the network system (that is, the protocol stack that the Windows
Sockets DLL runs over), the network interface, or the local network itself.

WSAENETRESET
(10052)
Network dropped connection on reset.
The connection has been broken due to keep-alive activity detecting a failure
while the operation was in progress. It can also be returned by setsockopt if
an attempt is made to set SO_KEEPALIVE on a connection that has already failed.

WSAENETUNREACH
(10051)
Network is unreachable.
A socket operation was attempted to an unreachable network. This usually means
the local software knows no route to reach the remote host.

WSAENOBUFS
(10055)
No buffer space available.
An operation on a socket could not be performed because the system lacked sufficient
buffer space or because a queue was full.

WSAENOPROTOOPT
(10042)
Bad protocol option.
An unknown, invalid or unsupported option or level was specified in a getsockopt
or setsockopt call.

WSAENOTCONN
(10057)
Socket is not connected.
A request to send or receive data was disallowed because the socket is not connected
and (when sending on a datagram socket using sendto) no address was supplied.
Any other type of operation might also return this error—for example,
setsockopt setting SO_KEEPALIVE if the connection has been reset.

WSAENOTSOCK
(10038)
Socket operation on nonsocket.
An operation was attempted on something that is not a socket. Either the socket
handle parameter did not reference a valid socket, or for select, a member of
an fd_set was not valid.

WSAEOPNOTSUPP
(10045)
Operation not supported.
The attempted operation is not supported for the type of object referenced.
Usually this occurs when a socket descriptor to a socket that cannot support
this operation is trying to accept a connection on a datagram socket.

WSAEPFNOSUPPORT
(10046)
Protocol family not supported.
The protocol family has not been configured into the system or no implementation
for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT.
However, it is interchangeable in most cases, and all Windows Sockets functions
that return one of these messages also specify WSAEAFNOSUPPORT.

WSAEPROCLIM
(10067)
Too many processes.
A Windows Sockets implementation may have a limit on the number of applications
that can use it simultaneously. WSAStartup may fail with this error if the limit
has been reached.

WSAEPROTONOSUPPORT
(10043)
Protocol not supported.
The requested protocol has not been configured into the system, or no implementation
for it exists. For example, a socket call requests a SOCK_DGRAM socket, but
specifies a stream protocol.

WSAEPROTOTYPE
(10041)
Protocol wrong type for socket.
A protocol was specified in the socket function call that does not support the
semantics of the socket type requested. For example, the ARPA Internet UDP protocol
cannot be specified with a socket type of SOCK_STREAM.

WSAESHUTDOWN
(10058)
Cannot send after socket shutdown.
A request to send or receive data was disallowed because the socket had already
been shut down in that direction with a previous shutdown call. By calling shutdown
a partial close of a socket is requested, which is a signal that sending or
receiving, or both have been discontinued.

WSAESOCKTNOSUPPORT
(10044)
Socket type not supported.
The support for the specified socket type does not exist in this address family.
For example, the optional type SOCK_RAW might be selected in a socket call,
and the implementation does not support SOCK_RAW sockets at all.

WSAETIMEDOUT
(10060)
Connection timed out.
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.

WSATYPE_NOT_FOUND
(10109)
Class type not found.
The specified class was not found.

WSAEWOULDBLOCK
(10035)
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be
completed immediately, for example recv when no data is queued to be read from
the socket. It is a nonfatal error, and the operation should be retried later.
It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect
on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection
to be established.

WSAHOST_NOT_FOUND
(11001)
Host not found.
No such host is known. The name is not an official host name or alias, or it
cannot be found in the database(s) being queried. This error may also be returned
for protocol and service queries, and means that the specified name could not
be found in the relevant database.

WSA_INVALID_HANDLE
(OS dependent)
Specified event object handle is invalid.
An application attempts to use an event object, but the specified handle is
not valid.

WSA_INVALID_PARAMETER
(OS dependent)
One or more parameters are invalid.
An application used a Windows Sockets function which directly maps to a Win32
function. The Win32 function is indicating a problem with one or more parameters.

WSAINVALIDPROCTABLE
(OS dependent)
Invalid procedure table from service provider.
A service provider returned a bogus procedure table to Ws2_32.dll. (Usually
caused by one or more of the function pointers being null.)

WSAINVALIDPROVIDER
(OS dependent)
Invalid service provider version number.
A service provider returned a version number other than 2.0.

WSA_IO_INCOMPLETE
(OS dependent)
Overlapped I/O event object not in signaled state.
The application has tried to determine the status of an overlapped operation
which is not yet completed. Applications that use WSAGetOverlappedResult (with
the fWait flag set to FALSE) in a polling mode to determine when an overlapped
operation has completed, get this error code until the operation is complete.

WSA_IO_PENDING
(OS dependent)
Overlapped operations will complete later.
The application has initiated an overlapped operation that cannot be completed
immediately. A completion indication will be given later when the operation
has been completed.

WSA_NOT_ENOUGH_MEMORY
(OS dependent)
Insufficient memory available.
An application used a Windows Sockets function that directly maps to a Win32
function. The Win32 function is indicating a lack of required memory resources.

WSANOTINITIALISED
(10093)
Successful WSAStartup not yet performed.
Either the application has not called WSAStartup or WSAStartup failed. The application
may be accessing a socket that the current active task does not own (that is,
trying to share a socket between tasks), or WSACleanup has been called too many
times.

WSANO_DATA
(11004)
Valid name, no data record of requested type.
The requested name is valid and was found in the database, but it does not have
the correct associated data being resolved for. The usual example for this is
a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName)
which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating
the host itself exists, but is not directly reachable.

WSANO_RECOVERY
(11003)
This is a nonrecoverable error.
This indicates some sort of nonrecoverable error occurred during a database
lookup. This may be because the database files (for example, BSD-compatible
HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was
returned by the server with a severe error.

WSAPROVIDERFAILEDINIT
(OS dependent)
Unable to initialize a service provider.
Either a service provider’s DLL could not be loaded (LoadLibrary failed) or
the provider’s WSPStartup/NSPStartup function failed.

WSASYSCALLFAILURE
(OS dependent)
System call failure.
Returned when a system call that should never fail does. For example, if a call
to WaitForMultipleObjects fails or one of the registry functions fails trying
to manipulate the protocol/name space catalogs.

WSASYSNOTREADY
(10091)
Network subsystem is unavailable.
This error is returned by WSAStartup if the Windows Sockets implementation cannot
function at this time because the underlying system it uses to provide network
services is currently unavailable. Users should check:
That the appropriate Windows Sockets DLL file is in the current path.
That they are not trying to use more than one Windows Sockets implementation
simultaneously. If there is more than one Winsock DLL on your system, be sure
the first one in the path is appropriate for the network subsystem currently
loaded.
The Windows Sockets implementation documentation to be sure all necessary components
are currently installed and configured correctly.

WSATRY_AGAIN
(11002)
Nonauthoritative host not found.
This is usually a temporary error during host name resolution and means that
the local server did not receive a response from an authoritative server. A
retry at some time later may be successful.

WSAVERNOTSUPPORTED
(10092)
Winsock.dll version out of range.
The current Windows Sockets implementation does not support the Windows Sockets
specification version requested by the application. Check that no old Windows
Sockets DLL files are being accessed.

WSAEDISCON
(10101)
Graceful shutdown in progress.
Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated
a graceful shutdown sequence.

WSA_OPERATION_ABORTED
(OS dependent)
Overlapped operation aborted.
An overlapped operation was canceled due to the closure of the socket, or the
execution of the SIO_FLUSH command in WSAIoctl.

Connect Error 10060 is a connection-timeout error that occurs when trying to connect to the web, such as when the system can not connect to the Internet Service Provider mail server in the required period of time. This error often occurs when you try and connect in PASV mode that prefers PORT for data connections to a server.

Another source for this problem could be the fact that it is connected to a slow proxy. Regardless of what the underlying cause of the error is, this is what you can do to solve the problem.

What is Connect Error 10060?

A 10060 timeout error in a Windows Winsock connection occurs when you try to access a site that is experiencing a high volume of visitors or when you try to connect to a server that does not exist. Microsoft has a patch that you can download (see the References section) and run to resolve this problem.

But by taking some simple steps on your own and editing the information on your computer’s registry, you can quickly resolve the problem without downloading and installing any software.

Error messages:

• Winsock 10060
• Winsock error # 10060
• Win32 error 10060 anydesk
• A connection to the Win32_10060 anydesk network could not be made.

Causes of Connect Error 10060

There are many causes why we can receive the message socket error 10060 connection wait time exhausted. Among them, we can highlight a bad connection, high latency, the server does not exist, etc. But we will not delve into the causes and if in the final way to solve this error.

As mentioned earlier, this error usually occurs because you are using a proxy server and there is not enough time for the connection to load the web page. This, in turn, causes the connection to run out.

How to identify Socket Error 10060 on your system?

First things first: how do you know you are dealing with Socket Error 10060? There are some things you can look for to recognize this problem.

A pretty obvious sign is the following message that appears on the screen when you try to connect to the Internet through a proxy server:

Another potential problem could be an inability of the browser to display the web page, in which case you should try to simply refresh that page (or wait a bit to see if the problem is solved) or open the file: // home page and then search for any useful information there.



A variation of the error message shown above is “10060 – Connection timeout”, which basically informs you of the same problem.

Finally, there is one more message that accompanies the same problem again, but this time it takes a totally different form, and that is “HTTP Error 404404 Not Found”.

In this case, the server can not obtain the file or script that you requested. In the beginning, you can try to update the page or verify if you have entered the correct URL. Usually, it’s as simple as that. However, if this is not enough to solve the problem, you should talk to your system administrator about it.

How to fix socket error 10060

Since the causes of this problem are several, it is normal to have different solutions. Below you will find the solution that repairs in almost 100% of cases the problem and others that serve as complementation.

Since Socket Error 10060 is related to the time it takes your browser to load a particular web page, one thing you could do to solve the problem is to increase the time limit required by the proxy service to load that web page.

If you have never done it and you have no idea where to start, do not fear, we are here to help you! Follow the guide we are about to outline, and you should be able to complete the task in a short time.

However, before you begin, it would be a good idea first to back up the log files. By doing this, you are protecting yourself against any kind of problem you may encounter along the way and, therefore, you can be sure that, whatever happens, you will always have the original configuration to fall back on. Well, here is what you should do next:

# Fix 1: Registry Edit

1. Go to Start, then Run, and type “regedit” followed by clicking OK.

2. Now find this registry subkey:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesW3ProxyParameters

3. Once you have selected that, click on RequestTimeoutSecs and then click on the Modify button.

4. Click on the decimal and modify the figure for the load time of the web page. If you are not sure what the value should be, we suggest at least 180.

5. Again, press the OK button and then restart your computer to complete the process.

With this, the connection timeout problem must be fixed. If you continue to receive the same error even after following these steps, try increasing the load time of the web page to at least 300.

Fix 2: Registry Edit (option 2)

1. Open the ” Registry Editor ” by clicking on the “Start” menu and then selecting “Run.” Type “Regedt32.exe” in the “Run” dialog box and click “OK.” Now you should see the ” Registry Editor “window.

2. Open the “Edit” menu and click on “Add value.”

3. Write the following information in the following window that appears:

4. Value name: TcpMaxDataRetransmissions Value type: REG_DWORD – Number Valid range: 0 – 0xFFFFFFFF Default value: 5 Decimal New value: 10 Decimal

5. Click on “OK.”

6. Close the ” Registry Editor ” and restart the computer. Test your connectivity once the computer has completely rebooted to see if the error occurs “10060 – Timeout has run out”.



Option 3: Solve socket error 10060 by proxy

1. Press the « Windows + R «keys.

2. Now, in the window that opens, type ” inetcpl.cpl ” and press ” Enter.”

3. Click on the « Connections » tab of the « Properties: Internet «window.

4. Click on the « LAN Configuration «button.

5. Uncheck the box ” Use a proxy server for the LAN ” and click on ” Accept.”

6. Check that the error has disappeared.

How to fix socket error 10060 Citrix

Many have experiences socket error 10060 Citrix NetApp while trying to a Microsoft ‘Remote Desktop’. If you are trying to connect to our desktop in the office and getting the Socket Error as below

Unable to connect the server contact your system administrator with following error: there is no Citrix Xenapp server configured on the specified server. (Socket error 10060)

This Published remote desktop application would be available on one or more servers.  If it is multiple servers, Citrix will automatically load your session to another appropriate server. If waiting to try again doesn’t fix the socket error 10060 on Citrix. Here are a few fixes to try before contacting your IT support or Citrix.

• If there is an Antivirus software installed, try to disable it then test again.
• Check your firewall to make sure ports 1494 and 2598 are open

Sometimes, Citrix could not be configured properly or has no servers assigned. This is an external Citrix Workspace error and therefore you would need to engage your company IT/Citrix support team to address the problem. This would be most cases as it would be an error from your IT workplace.

Final notes

This type of error causes that the fps of the games go down, that Gmail, Outlook Express, Opera, Office 365, Windows 7, 8, 10, delphy, etc. give problems. In general, the parameters mentioned above must be modified to get a connection, but it does not always work, since the error may come from something alien to us.