Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.


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

General Network Configuration & Implementation Issues

Table of contents
Created by Marlo Bidayan, last modified by Alejandro Realo on Nov 02, 2016

Views: 76 Votes: 0 Revisions: 6


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:31
The graphic device driver supports more than one (1) planes.

System Error: 51
Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off.  If Windows still cannot find the network path, contact your network administrator.

System Error: 53
The network path was not found.

System Error: 1300
Not all privileges or groups referenced are assigned to the caller.

System Error: 1707
The network address is invalid.

System Error: 1814
The specified resource name cannot be found in the image file.

Winsock Connect Error:
System Error: 10050
Network is down. This error may be reported at any time if the Windows Sockets implementation detects an underlying failure.  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.

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.

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.

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

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.

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. 

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:

  • System Error Codes

  • Windows Sockets Error Codes


Last modified
12:54, 2 Nov 2016