| Event Id | 10035 |
| Source | Winsock |
| Description | Socket is not connected. |
| Event Information | According to Microsoft: EXPLANATION: A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket) no address was supplied. An application attempted an input/output network function call before establishing an association with a remote socket (i.e. before calling connect() or accept(). USER ACTION: Open a connection to the remote source using the current application. If you were previously connected, try reconnecting. Ping the remote host you were connected to. If it does not respond, it might be off-line or there might be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again). In addition, ping a local host to verify that your local network is still functioning. For a serial connection, ping your local router address. If you are on a serial connection, your local router is the IP address of the host you initially logged on to using SLIP or PPP. In addition, ping a host on the same subnet as the host you were connected to (if you know of one). This will verify that the destination network is functioning. Use the tracert command at the command prompt to determine the path to the host you were connected to. This will not reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way. |
| Reference Links | Socket is not connected |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.