Cannot Connect Socket Error # 11001
Contents |
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript
Socket Error 11001 Host Not Found Windows 7
.NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics socket error 11001 error number 0x800ccc0d Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center
Socket Error 11001 H1z1
Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish socket error 11001 error number 0x800ccc0d outlook express Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote what is a socket error Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Networking and Internet Windows Sockets 2 Winsock Reference Winsock Reference Windows Sockets Error Codes Windows Sockets Error Codes Windows Sockets Error Codes Socket Options Winsock IOCTLs Winsock Annexes Winsock Enumerations Winsock Functions Winsock Structures and Typedefs Winsock Tracing Events Winsock SPI Windows Sockets Error Codes TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Sockets Error Codes Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic. The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be used to obtai
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 19:56:20 GMT by s_hv972 (squid/3.5.20)
by CloudFlare Ray ID: 2ed6447ec1ee3012
ease planning, as well. Free PRTG Download >> What is this? This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions! Learn more Top Tags 5721× prtg 1832× snmp 1460× sensor 930× wmi 620× notifications 463× maps View all Tags How do I solve a Connection Refused Socket Error # 10061 in Enterprise Console? Votes:0 Your Vote: Up Down When I try to connect to PRTG via the Enterprise Console, the software displays a socket error number 10061 and I cannot connect. However, I can still login to the PRTG web interface. What settings do I have to change to solve this? Why does the connection not work? enterprise-console error gui login prtg server-administrator windows Created on Feb 3, 2010 9:00:13 AM by Daniel Zobel [Paessler Support] Last change on Dec 7, 2012 3:15:58 PM by Gerald Schoch [Paessler Support] Permalink 1 Reply Accepted Answer Votes:0 Your Vote: Up Down This article applies to PRTG Network Monitor 14 or later Solving Connection Refused Socket Error # 10061 in the Enterprise Console The Enterprise Console is a native Windows application and one of the interfaces that you can use to change settings and review monitoring data of your PRTG setup. In order to retrieve this data, the Enterprise Console must establish a connection to the PRTG Web Server. If you open the PRTG Enterprise Console and see a "socket error number 10061", this means that your Enterprise Console was not able to connect to the PRTG Web Server running on the PRTG Core Server. There can be several reasons for this. If you can still log into the PRTG Web Interface but get this error message using the Enterprise Console, the most common matter is non-matching settings of Web Server and Enterprise Console. Step 1: Viewing the Enterprise Console Settings From the Windows Start Menu, open the PRTG Enterprise Console application. From the menu, select File | Manage PRTG Server Connections. The Devices overview appears. On the left side, click on PRTG Server Connections. On the right side, select a server entry and click on the edit Edit button (the wrench symbol). You see the settings the Enterprise Console uses to connect to the PRTG Web Server. Step 2: Viewing the PRTG Administration Tool Settings From the Windows Start Menu, open the PRTG Administration Tool on the machine that is running your PRTG Core Server. In the Web Server tab, you can view the section Select IP Address for PRTG's Web Server denoting the IPs that are allowed to establish a connection to the Web Server. The