Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > General Network Configuration & Implementation Issues

General Network Configuration & Implementation Issues

Table of contents

Updated July 7th, 2017


This article provides information about the general network configuration and implementation issues.


  • All versions of DameWare Remote Support
  • All versions of DameWare Mini Remote Control


System errors are Microsoft Operating System errors, not DameWare System errors. Winsock errors are Microsoft Windows Sockets (TCP) errors as well. The vast majority of all Operating System errors encountered while using the DameWare NT Utilities or DameWare Mini Remote Control programs (i.e. System Errors, Winsock Errors, etc.) are not directly related to DameWare software. These issues are directly related to some type of system or network configuration issue within a network environment and can usually be duplicated outside of DameWare software.

The following are some examples of network configuration & implementation issues, along with some additional links that may help troubleshoot these specific issues in the environment:


System Error: 53
The network path was not found.
Error 53: Network path was not found



System Error: 1707
The network address is invalid.
System error 1707 - The Network Address is Invalid


Winsock Connect Error:
System Error: 10054
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.

Troubleshooting Winsock 10054 errors


Winsock Connect Error:
System Error: 10060
System Message:
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.

Troubleshooting Winsock 10060 Errors when using DameWare


Winsock Connect Error:
System Error: 10061
System Message:
No connection could be made because the target machine actively refused it.

Troubleshooting the Connection Refused Message - TCP/IP Error 10061


Winsock Connect Error:
System Error: 11001
System Message:
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 the specified name could not be found in the relevant database.

Troubleshooting Winsock 11001 Errors


Winsock Connect Error:
System Error: 11004
System Message:
The requested name is valid and was found in the database, but it does not have the correct associated data for which it is being resolved.

Troubleshooting TCP-IP Error 11004 - The requested name is valid and was found in the database - but it does not have the correct associated data being resolved for


It is also possible to receive other errors that are not listed here by default.  For a listing of all Microsoft Operating System error, please refer to the following Microsoft Knowledge Base articles:




Last modified
12:16, 23 Aug 2017