Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
troubleshooting:testing-connection-with-traceroute [2010-03-04 18:12:58]
garrett.plasky 		troubleshooting:testing-connection-with-traceroute [2010-04-06 20:40:52]
garrett.plasky
Line 12: Line 12:
 At the command prompt, enter <c>tracert yourdomain.com</c>, where your domain is a domain name on your server or your server's IP address. This will result in something like the following (the first two host lines have been intentionally blanked): At the command prompt, enter <c>tracert yourdomain.com</c>, where your domain is a domain name on your server or your server's IP address. This will result in something like the following (the first two host lines have been intentionally blanked):
  
-{{:troubleshooting:tracert.png?200&direct|Traceroute Results}}+{{ :troubleshooting:tracert.png?200&direct |Traceroute Results}}
  
 =====Interpreting Results===== =====Interpreting Results=====
Line 18: Line 18:
  
 The above example shows a successful trace without any unreachable hosts. If your trace dies out after a specific hop by only returning full lines of asterisks ("* * * *"), then chances are the issue is at or just after the hop before the asterisks began. The above example shows a successful trace without any unreachable hosts. If your trace dies out after a specific hop by only returning full lines of asterisks ("* * * *"), then chances are the issue is at or just after the hop before the asterisks began.
 +
 +Large jumps in response times can also mean a possible issue. If you are consistently seeing around 5ms for your first 3 hops, for example, and then on the 4th hop the response time jumps to 500ms, then there may be an issue with the 4th hop.
  
 =====Sending Us the Results===== =====Sending Us the Results=====