Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare - Knowledgebase Articles > Troubleshooting Winsock 11001 Errors

Troubleshooting Winsock 11001 Errors

Table of contents

Updated June 27th, 2017

Overview

Winsock Connect Error 11001
Host not found. 
No such host is known.

 

The name is not an official HostName 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. 

Environment

  • Dameware All versions

Detail

Winsock Errors are Microsoft Windows Sockets errors, and a Winsock 11001 error implies some type of Names Resolution issue (i.e. DNS, WINS, Hosts, LMHosts, etc.) within the network environment.  Therefore, this behavior can be duplicated outside of DameWare software by attempting to ping the remote machine using the same information supplied in the DameWare Mini Remote Control (DMRC) Remote Connect dialog. Once the Names Resolution issue is resolved, DameWare software will be able to connect to the remote machines using the specified information (Host Name, FQDN, etc.).  However, using the IP address instead may prove to be helpful.

 

 

 

Last modified

Tags

This page has no custom tags.

Classifications

Public