Tools
General Network Configuration & Implementation Issues for Dameware
This article provides information about the general network configuration and implementation issues for Dameware.
First published date
Last published date
Overview
Product section
Resolution
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 Remote Support (formerly Dameware NT Utilities) or Dameware Mini Remote Control programs (for example, system errors or Winsock errors) 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
ERROR_BAD_NETPATH
The network path was not found.
Error 53: Network path was not found in Dameware Remote Support
System Error: 1707
RPC_S_INVALID_NET_ADDR
The network address is invalid.
Dameware 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 in Dameware
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 in Dameware Mini Remote Control - 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.
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.
Dameware Troubleshooting TCP-IP Error 11004 - The requested name is valid and was found in the database
- How to use the Proxy functionality within the Dameware Mini Remote Control program
- The Simple File Transfer (SFT) shell menu may not be available in Dameware
- Creating an MSI Package with the Dameware Mini Remote Control Client Agent MSI Builder
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 (© 2017 Microsoft, available at https://msdn.microsoft.com, obtained on July 7, 2017.)
- Windows Sockets Error Codes (© 2017 Microsoft, available at https://msdn.microsoft.com, obtained on July 7, 2017.)
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.