10.3.tracert command

• If the ping were unsuccessful, or if the roundtrip response times seem too long, the tracert command might help isolate the issue.

• The tracert command pings every router hop from the source to the destination and reports the round-trip time for each router hop.

• If a router is not reachable, you might want to investigate the router hop just before or just after the hop that timed out.

Example 1: Sample Output from a Successful Windows tracert Command

• This example shows a successful trace from a PC to a destination of pearsonitcertification.com.

• Even though the trace was successful, the output still helps identify any slow links interconnecting routers along the path from the source to the destination.

C:\> tracert pearsonitcertification.com
Tracing route to pearsonitcertification.com [64.28.85.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms THE-WALLACES-TI [192.168.1.1]
2 12 ms 18 ms 9 ms CPE-76-177-16-1.natcky.res.rr.com [76.177.16.1]
3 8 ms 13 ms 11 ms gig2-0-0.rcmdky-mx41.natcky.rr.com
[65.28.199.205]
4 32 ms 35 ms 34 ms tge0-2-0.chcgileq-rtr1.kc.rr.com [65.28.199.97]
5 30 ms 28 ms 35 ms ae-4-0.cr0.chi10.tbone.rr.com [66.109.6.100]
6 28 ms 36 ms 51 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
7 32 ms 37 ms 32 ms if-4-0-0.core1.CT8-Chicago.as6453.net
[66.110.14.21]
8 32 ms 31 ms 33 ms if-1-0-0-1878.core2.CT8-Chicago.as6453.net
[66.110.27.78]
9 58 ms 60 ms 56 ms 63.243.186.25
10 95 ms 64 ms 73 ms cr2-pos-0-8-0-3.nyr.savvis.net [208.173.129.29]
11 66 ms 61 ms 72 ms hr1-tengig-13-0-0.waltham2bo2.savvis.net
[204.70.198.182]
12 62 ms 67 ms 62 ms das3-v3038.bo2.savvis.net[209.202.187.182]
13 62 ms 63 ms 66 ms blhosting.bridgelinesw.com [64.14.81.46]
14 63 ms 62 ms 76 ms www1.webdialogs.com [64.28.85.25]
Trace complete.

Example 2: Sample Output from an Unsuccessful Windows tracert Command

• This example shows an unsuccessful trace. The first-hop router (192.168.1.1) responded; however, the router beyond that did not respond. So, in a troubleshooting situation, you might focus your attention to the interconnection between those two routers.

C:\> tracert 172.16.1.1
Tracing route to 172.16.1.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms THE-WALLACES-TI [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
OUTPUT OMITTED...