Appendix A Network Troubleshooting

The following examples show the typical output of this command:

C:\>tracert www.example.com

Tracing route to www.example.com [192.0.32.10] over a maximum of 30 hops:

1

<1 ms

<1 ms

<1 ms

172.23.x.x

2

5

ms

4

ms

5

ms

172.23.x.x

3

4

ms

4

ms

4

ms

172.23.x.x

4

5

ms

4

ms

6

ms

219-87-158-97.static.tfn.tw [219.87.158.97]

5

6

ms

5

ms

4

ms

10.42.232.150

6

5

ms

4

ms

4

ms

hc-c12r2.router.tw [220.128.7.86]

7

10

ms

7

ms

10

ms

tp-s2-c12r12.router.tw [220.128.2.90]

8

9

ms

7

ms

8

ms

pr03-s2.tp.tw [220.128.4.181]

9

6

ms

6

ms

9

ms

220-128-3-249.NET-IP.tw [220.128.3.249]

10

138

ms

137

ms

138

ms

r11-pa.NET-IP.net [211.72.108.129]

11

138 ms

138 ms

138 ms

po4-0.core01.sjc04.atlas.com [154.54.11.129]

12

128

ms

139

ms

140

ms

te9-2.mpd01.sjc04.atlas.com [154.54.0.173]

13

140

ms

139

ms

136

ms

61.58.33.173

14

154

ms

153

ms

137

ms

xe-0-0-0.r20.gin.ntt.net [129.250.16.161]

15

154

ms

154

ms

137

ms

as-2.r21.tokyjp01.jp.ntt.net [129.250.4.81]

16

562

ms

553

ms

553

ms

38.106.6.34

17

554

ms

554

ms

553

ms

po-2.r00.lsanca19.us.ntt.net [129.250.6.42]

18

254

ms

254

ms

248

ms

204.1.254.150

19154 ms 253 ms 154 ms 192.0.32.10 Trace complete.

C:\>

Here, the tracert to www.example.com took 18 hops to reach its destination. Looking at the latency data, you’ll see the first slow down happens at hop 10.

The extremely low latency on the first few hops indicates a network local to the computer where the tracert command originated, such as a home or office LAN. The packets then move onto the local WAN (such as your Internet Service Provider’s network). Because of the close proximity of those servers to your computer, the latency remains low.

Once the data packets move out of the regional network to the first international server (at hop 10 in this example), the latency increases. This is because of the distance between the regional and international servers - it physically takes longer for the response to get back to your computer.

Finally, on transition hop 15 from the server in Japan to the server in California, another latency spike occurs. If you were having connection problems, this would most likely be the source of it. For whatever reason, the server in Japan has a less than optimal connection with its counterpart in the United States.

260

 

P-870HN-51D User’s Guide