TCP error code 10060: 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

6/3/2019 4:15 PM

9/3/2025 10:43 PM

The following error is displayed in the SolarWinds Platform Web Console:

Could not connect to net.tcp://<redacted>:17777/orion/ncm/businesslayer. The connection attempt lasted for a timespan of 00:00:21.0470449. TCP error code 10060

 

The logs include the following additional information:

TCP error code 10060: 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 <IP_adress>:<port_number>.

 

For example:

TCP error code 10060: 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 <redacted>:17777.

 

Orion Platform

TCP error code 10060 is usually caused by either:

• DNS issues
• A port being blocked

To determine if a port is being blocked:

1. Check the log to determine the affected IP address and port number.
   In the example above, the IP address is 10.92.234.137 and the IP address is 17777. Port 17777 is required by SWIS and the BusinessLayer.
2. Verify that both the primary SolarWinds Platform server and any additional web servers (AWS) can reach port 17777 on the server with the specified IP address. To do this, open a command prompt on the primary server and the AWS and issue the following command:

   telnet <IP_address> <port_number>

For example:

A blank output indicates a successful connection. If the connection fails, you will see the following message:

Connecting To <IP_address>...Could not open connection to the host, on port <port_number>: Connect failed

 

If the connection fails, check your firewall configuration or perform a packet capture to determine why the connection failed.