KB Logo

TOLIS Group Knowledge Base

Browse KB by category:
Go to KB #:
Email   Bookmark

What does 'Connection Reset by Peer' mean?

Views: 28241
Votes: 1
Posted: 09 Jan, 2008

What does it mean?

A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or a restart. On a datastream socket, the connection was reset. This reset could be generated locally by the network system when it detects a connection failure, or it might be received from the remote host (in TCP terms, the remote host sent a reset packet). 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.

What can you do?

Check the following:

  1. Ping the remote host you were connected to. If it doesn't respond, it might be offline or there might be a network problem along the way. If it does respond, 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).
  2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step).
  3. 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 .
  4. 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. Type tracert (Windows) or traceroute (Linux/Unix/Mac OS X ) at the command prompt to determine the path to the host you were connected to. This won't 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. 

    The output of your traceroute command on Linux, Unix or Mac OS X may look something like:

    $ traceroute -n www.google.com
    traceroute to www.google.com (, 30 hops max, 40 byte packets
     1  1.254 ms  1.242 ms  1.240 ms
     2  5.933 ms  7.538 ms  8.415 ms
     3  12.305 ms  10.725 ms  11.466 ms
     4  14.038 ms  12.962 ms  14.778 ms
     5  15.610 ms  16.402 ms  17.283 ms
     6  18.921 ms  16.985 ms  18.564 ms
     7  40.993 ms  38.154 ms  38.837 ms
     8  38.825 ms  38.876 ms  38.756 ms
     9  40.172 ms  38.957 ms  40.201 ms
    10  42.816 ms  42.797 ms  43.106 ms
    11  44.374 ms  44.904 ms  44.845 ms
    12  44.906 ms  43.433 ms  43.227 ms
    13  50.209 ms  50.821 ms  49.009 ms
    14  43.488 ms  45.520 ms  46.350 ms

    On Windows, your tracert command may result with something similar to:

    > tracert -d www.google.com

    Tracing route to www.l.google.com []
    over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms
      2     1 ms     1 ms     1 ms
      3     4 ms     5 ms     4 ms
      4     4 ms     4 ms     4 ms
      5     7 ms     5 ms     6 ms
      6     6 ms     6 ms     6 ms
      7    37 ms    37 ms    37 ms
      8    38 ms    37 ms    39 ms
      9    37 ms    38 ms    38 ms
     10    44 ms    44 ms     *
     11    42 ms    47 ms    44 ms
     12    43 ms    43 ms    45 ms
     13    47 ms    55 ms    42 ms
     14    42 ms    42 ms    43 ms

    Trace complete.

These commands with results are provided as examples are are not certain to be the results that you may see upon running these commands.  For more information or questions about running commands on your systems, please contact your OS manufacturer.  TOLIS Group assumes no liability for commands run on your system as a result of reading this article.

Others in this Category
document Important LTO-4 SAS and SAS HBA Information
document Image based backups versus file-by-file backups. Competitive or Complimentary Technologies?
document Big Endian vs. Little Endian. What does this mean?
document Disable/Enable Hardware Compression When Using BRU
document Information on FireWire Cables
» More Articles

Powered by KnowledgebasePublisher
Page Load Time: 0.038342 seconds / 38.342 milliseconds.
Page File Size: 31062 bytes.