Deprecated: Assigning the return value of new by reference is deprecated in /home/alpinesu/public_html/knowledgebase/global.php on line 173

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/alpinesu/public_html/knowledgebase/global.php:173) in /home/alpinesu/public_html/knowledgebase/inc/ on line 111

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/alpinesu/public_html/knowledgebase/global.php:173) in /home/alpinesu/public_html/knowledgebase/inc/ on line 111
How to perform a Traceroute .: Alpine Support Knowledge Base
Domain Names Dedicated Servers Templates
Alpine Support Knowledge Base Glossary   
Browse by Category
Alpine Support Knowledge Base .: Quick Help .: How to perform a Traceroute

How to perform a Traceroute

Perform a Trace Route
A trace route attempts to report on the current status of an internet connection at all locations between your computer and the destination.

1) Enter your DOS prompt: Click Start | Programs | AccessoriesCommand Prompt
2) Goto your base directory C:
3) Use the tracert DOS command.

For example, if you are testing the internet connection to this server:

C:>tracert >> Trace.txt

If you are testing the internet connection to a different computer, you must specify its address instead of this servers address. This command will create a text file named Trace.txt that you can e-mail to the lagging node.

To find this file:

4) Goto your Desktop.
5) Double-click on My Computer.
6) Double-click on Drive C:.
7) Search in this folder for Trace.txt.
8) Open Trace.txt to view results.

Reading a Trace Route
For example, the trace route displays:

#LatencyIP address
1133 133293.131.222.1
2140 007297.121.444.1
3824 801299.999.999.9
4165 -665204.146.98.4

The first number is the internet hop or node number (1, 2, 3, 4, ...).

The next numbers is the latency or lag (133, 133, 140, 007, ...), measured in milliseconds that it took to receive a reply (1000 ms = 1 second).

Any result over 500 ms, or any result that times out indicates that node has lag.

If some results display * (an asterisk) instead of milliseconds, then that node took much longer than allowed to respond. It timed out.

The last number is the Internet address ( ...) of that internet node.

In this example, there is a source of lag of 824 ms. It is is underlined here:

#LatencyIP address 
1133 133293.131.222.1 
2140 007297.121.444.1 
3824 801299.999.999.9< Lag Source
4165 -665204.146.98.4 

How helpful was this article to you?

Related Articles

User Comments

Add Comment
No comments have been posted.

.: Powered by Lore 1.5.9
Copyright ©2001 - 2006   Alpine Internet ABN 65 109 918 747