Winsock 10060

Winsock 10060 errors are TCP timeout errors, which typically means that the Mini Remote Control program contacted some remote machine, but then the data packets never made it back to the local machine, hence the timeout. If you are working over a VPN connection, there could also be some type of routing issue. I have also seen 10060 errors if the remote machine was in "Power Saver" mode (i.e. hibernating).

Here is some additional information about the 10060 error:

WSAETIMEDOUT (10060)

Connection timed out.

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

The Winsock 10060 error is not directly related to our software. This is a TCP timeout error and it can be duplicated outside of our software.

1. You can try adjusting your Compression & Scan Block settings. Setting compression to 9 and increasing your Scan Blocks will minimize the size of the packets sent across the pipe. Changing the compression to 9 will compress the data as much as it can before sending the data packet. Increasing the Scan Blocks will divide the remote monitor display into an increased number of "bands" or rows. Initially, the entire screen is send over and displayed on your monitor. After the initial screen is displayed, only the bands that change are sent from the remote machine back to yours, thus reducing the amount of data being sent back and forth. You can also try the Set Resolution To: feature on the Remote Options Tab or the Force 4-bit or Force 8-bit settings in the Display Options Tab.

2. Although the Mini Remote Control (DMRC) program uses a single TCP port (default is TCP 6129) to establish a remote connect session, other ports are required to be open to remotely install the DMRC Client Agent Service, basically "File & Printer Sharing". The Mini Remote Control program will first attempt a TCP connection to the remote machine. If nothing is listening on the specified port (i.e. DMRC Client Agent Service not installed or a mismatch in TCP port usage), the DMRC program will drop out of it's TCP mode and use the installed protocols to attempt to interrogate the remote machine. Please also keep in mind that if the remote machine is on another Subnet or behind a router/firewall, then the necessary File & Printer Sharing ports must also be open on those routers/firewalls for the DMRC program to remotely install the DMRC Client Agent Service. The firewall article mentioned below describes the necessary "File & Printer Sharing" ports that the DMRC program uses to remotely install the DMRC Client Agent Service: http://www.dameware.com/support/faq/faq.asp?ID=FAQ1045

3. Please also make sure there is a network route to the remote host via the TCP protocol using the selected port (default port 6129). If you are dealing with a VPN connection (this would also apply to multiple subnets with a router in between) it is possible that the packet is being received by the remote machine and then the remote machine does not know how to route the packet back to you. In this scenario, I have had more than one customer say that adding a static route fixed it. (which can be made persistent, route -p add xxxxxxxxx mask yyyyyyyy <gateway> ) This has to be done on the remote machine. (see attached diagram)

4. Winsock 10060 errors can also be caused by firewall software blocking the necessary ports, provided this firewall software was not configured properly. Such as XP-SP2, ZoneAlarm, Black Ice, etc….