| Event Id | 10037 |
| Source | ISA Server |
| Description | Connection reset by peer. For more information about this event, see ISA Server Help. |
| Event Information | According to Microsoft: Cause: A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a time-out or a reboot. This error is also possible on a datagram socket. For instance, this error could result if your application sends a UDP datagram to a host, which rejects it by responding with an ICMP Port Unreachable. Resolution: You can attempt to reestablish the connection. Report the problem to your network administrator or check the connection logs for other servers on the network for more information. In addition you can 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). You can also 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. 5. 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 | Connection reset by peer. |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.