Some Network Troubleshooting Tips- Part: 2

• TRACERT

TRACERT in Windows (TRACEROUTE in Unix) is short for “trace route”.
This basically is a trace of the route that a communication between two
computers takes.

TRACERT is used to test a lag in communication or the point of network failure
on a network (Intranet or Internet) that is causing poor to no connection between
two computers. TRACERT sends pings to each of the computers along a route
and responds with that data on each “hop”.

If at one point during the trace all responses stop, it can help identify the source
of network connectivity issues and whether they are caused by internal or
external network conditions. For example, if an Internet Service Provider’s
Router is not responding, the network issues are external.
Usage of TRACERT

H:\>tracert
Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name
Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.
Example:
In the examples below, all bold text represents what is typed in at the command
prompt. All italicized text represents what displays in response to what was just
typed.
NOTE An asterisk (*) indicates that there was no response for that PING. It is not
uncommon to see one asterisk on a “hop”.

H:\>tracert 216.239.57.99
Tracing route to 216.239.57.99 over a maximum of 30 hops
1 <10 ms <10 ms <10 ms 10.4.3.2
2 <10 ms <10 ms <10 ms internal.server.com [10.4.3.3]
3 <10 ms 16 ms <10 ms 204.50.32.34

4 <10 ms <10 ms <10 ms 192.168.12.13
5 31 ms <10 ms <10 ms internal2.server.com [10.4.4.2]
6 <10 ms 16 ms <10 ms internal3.server.com [10.5.3.2]
7 <10 ms <10 ms <10 ms 209.139.215.62
8 <10 ms <10 ms 16 ms 216.18.26.29
9 <10 ms <10 ms <10 ms ge4-1.wanb-vancbc.ip.grouptelecom.net
216.18.31.133]
10 <10 ms 15 ms <10 ms ge3-0.peera-sttlwa.ip.grouptelecom.net
[66.59.190.14]
11 16 ms <10 ms 16 ms bpr2-so-5-0-0.seattleswitchdesign.cw.net
[208.173.50.73]
12 <10 ms 15 ms 16 ms acr2-so-6-0-0.seattle.cw.net [208.172.81.186]
13 32 ms 15 ms 32 ms dcr1-loopback.santaclara.cw.net [208.172.146.99]
14 31 ms 31 ms 16 ms bhr1-pos-0-0.santaclarasc5.cw.net
[208.172.156.74]
15 15 ms 32 ms 31 ms csr21-ve243.santaclarasc4.cw.net [216.34.3.11]
16 31 ms 31 ms 31 ms google-exodus.exodus.net [64.41.147.62]
17 31 ms * 15 ms 216.239.49.2
18 31 ms 15 ms 32 ms 216.239.57.99
Trace complete.

Note that the trace goes through each component on the network until it reaches
its destination. Three PING response times are given for each “hop” on the
route that are show in milliseconds.