| Event Id | 10135 |
| Source | Winsock |
| Description | Connection refused. |
| Event Information | According to Microsoft: EXPLANATION: No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host. You might have gone to the wrong host, or the server application you are trying to contact might not be running. USER ACTION: Check the destination address you are using. If you used a hostname, verify that it was resolved to the correct address. If your hostname resolution uses a local host table, it is possible the name was resolved to an obsolete address. It is also possible that the local services file has an incorrect port number (although this is unlikely). You can verify that the remote computer is rejecting your connection attempt by checking the network statistics locally. If your network system has a WinSock utility such as ping or nbtstat that shows network statistics, use this to verify that you are receiving TCP resets or ICMP Port Unreachable packets each time you attempt to connect. Try again later. If connection is still refused, contact your network administrator. |
| Reference Links | Connection refused |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.