Jump to content

Tracert Packet Drop Investigation


Recommended Posts

Okay, new investigation.

 

Ice and myself has noticed that if we run a tracert to the server one of our hops are dropping out...consistently.

 

1 8 ms 9 ms 21 ms 10.18.168.1

2 9 ms 8 ms 9 ms 12-215-17-193.client.mchsi.com [12.215.17.193]

3 18 ms 19 ms 18 ms 12-215-2-138.client.mchsi.com [12.215.2.138]

4 30 ms 29 ms 28 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]

5 37 ms 29 ms 30 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

6 28 ms 46 ms 29 ms 4.68.127.165

7 * 27 ms * so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

8 29 ms 27 ms 28 ms ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

9 27 ms 28 ms 47 ms unknown.Level3.net [166.90.208.206]

10 61 ms 52 ms 28 ms 69.12.89.96

 

1 9 ms 27 ms 7 ms 10.18.168.1

2 8 ms 9 ms 8 ms 12-215-17-193.client.mchsi.com [12.215.17.193]

3 19 ms 18 ms 28 ms 12-215-2-138.client.mchsi.com [12.215.2.138]

4 33 ms 28 ms 28 ms tbr1-p012701.cgcil.ip.att.net [12.122.2.222]

5 31 ms 28 ms 53 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

6 30 ms 29 ms 27 ms 4.68.127.165

7 50 ms * 82 ms so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

8 30 ms 26 ms 26 ms ge-11-2.ipcolo2.Chicago1.Level3.net [4.68.101.16

9]

9 27 ms 28 ms 30 ms unknown.Level3.net [166.90.208.206]

10 30 ms 32 ms 29 ms 69.12.89.96

 

Disclaimer: this has nothing to do with our "SERVER" but it is a problem in the route to our server.

 

So, how should those that have the problem attempt to fix it??

Link to comment
Share on other sites

If we gather enough consistant data, like with traceroutes by several people pointing to the same router, then I would imagine XGS would have a better chance in addressing it.

 

That said, there may still be fallout from the fire...I just don't know. Anyoe else going through that exact router needs to post up.

Link to comment
Share on other sites

If you use pingplotter, you'll notice that the routing through the Chicago Level 3 area is "alive" so to speak. There are route changes nearly constantly. One of the major ones, however, gave me 1% packet loss. It just so happened to be the one on the route when my 300 samples were finished:

 

traceto1.png

 

It would be interesting to see if the percentages are as high as it seems when you only send the 3 packets involved with tracert.

 

btw, did you ever right-click on a server and use the traceroute in it?

Link to comment
Share on other sites

GC Alumni
(edited)

Two things.

 

FIrst, here is a sample tracert to the server. I'm seeing the same dropout server as Brillow.

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 10 ms 12 ms 19 ms 10.166.96.1

2 15 ms 66 ms 42 ms 68.86.118.125

3 15 ms 67 ms 18 ms 68.87.230.41

4 33 ms 36 ms 30 ms 68.87.230.254

5 60 ms 15 ms 34 ms 12.126.230.5

6 58 ms 47 ms 14 ms 12.123.6.74

7 13 ms 25 ms 32 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

8 17 ms 16 ms 15 ms 4.68.127.165

9 14 ms 58 ms * so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

10 20 ms 20 ms 58 ms ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

11 49 ms 15 ms 14 ms unknown.Level3.net [166.90.208.206]

12 52 ms 23 ms 15 ms 69.12.89.6

 

Trace complete.

-----------------------------------------------------------------------------------------------

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 12 ms 11 ms 11 ms 10.166.96.1

2 13 ms 12 ms 52 ms 68.86.118.125

3 14 ms 34 ms 12 ms 68.87.230.41

4 15 ms 17 ms 16 ms 68.87.230.254

5 16 ms 19 ms 38 ms 12.126.230.5

6 14 ms 17 ms 26 ms 12.123.6.74

7 50 ms 14 ms 18 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]

8 19 ms 14 ms 14 ms 4.68.127.165

9 * 17 ms 61 ms so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

10 47 ms 24 ms 22 ms ge-11-2.ipcolo2.Chicago1.Level3.net [4.68.101.169]

11 34 ms 22 ms 22 ms unknown.Level3.net [166.90.208.206]

12 15 ms 17 ms 15 ms 69.12.89.6

 

Trace complete.

 

I've done serveral tracerts over the past couple days and this is the only server I ever see a drop on. As Fatty mentioned it could still be fallout from before the fire. I don't have any data from before hand.

 

Just for reference I"m connectiong from Waukegan which is a northern suburb of Chicago and I"m on Comcast. Considing my closeness to the server I would think I wouldn't get any dropped packets...

 

Also for reference, I'd say from my trials I'm getting dropped about 1/2 the traces I've done. Not extermely scientific at this point yet though.

 

Second

What proggy do you use Fatty?

Edited by Ice_Berge_00
Link to comment
Share on other sites

who is your provider?

 

 

Tracing route to 69.12.89.96 over a maximum of 30 hops

 

1 1 ms 2 ms 1 ms homeportal.gateway.2wire.net [172.16.0.1]

2 16 ms 15 ms 15 ms ppp-69-221-7-254.dsl.toldoh.ameritech.net [69.22

1.7.254]

3 17 ms 17 ms 17 ms dist2-vlan60.toldoh.ameritech.net [65.42.7.243]

 

4 17 ms 17 ms 15 ms bb1-g8-0.toldoh.ameritech.net [65.42.7.115]

5 18 ms 19 ms 19 ms bb1-p1-2.sfldmi.ameritech.net [151.164.188.38]

6 19 ms 19 ms 19 ms bb2-p15-0.sfldmi.ameritech.net [151.164.40.182]

 

7 27 ms 27 ms 27 ms core2-p6-1.crchil.sbcglobal.net [151.164.242.129

]

8 28 ms 27 ms 29 ms core1-p1-0.crchil.sbcglobal.net [151.164.188.29]

 

9 28 ms 29 ms 27 ms bb1-p4-0.chcgil.ameritech.net [151.164.42.182]

10 28 ms 29 ms 27 ms bb2-p5-0.chcgil.ameritech.net [151.164.191.178]

 

11 30 ms 29 ms 29 ms ex1-p2-0.eqchil.sbcglobal.net [151.164.42.149]

12 31 ms 29 ms 29 ms ibx.ge-0-2-0.cr2.chi1.speakeasy.net [206.223.119

.4]

13 30 ms 31 ms 31 ms 69.12.89.96

 

Trace complete.

Link to comment
Share on other sites

Member
(edited)

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 <1 ms 1 ms <1 ms 192.168.0.1

2 19 ms 9 ms 9 ms adsl-68-76-111-254.dsl.bcvloh.ameritech.net [68.76.111.254]

3 9 ms 19 ms 14 ms dist1-vlan50.bcvloh.sbcglobal.net [66.73.20.226]

4 60 ms 57 ms 65 ms bb2-g2-3-0.bcvloh.sbcglobal.net [66.73.20.100]

5 14 ms 18 ms 12 ms core1-p5-3.crcloh.sbcglobal.net [151.164.41.195]

6 24 ms 30 ms 18 ms core1-p3-0.crhnva.sbcglobal.net [151.164.240.122]

7 21 ms 21 ms 22 ms bb1-p5-0.hrndva.sbcglobal.net [151.164.242.70]

8 18 ms 18 ms 19 ms ex1-p11-0.eqabva.sbcglobal.net [151.164.40.49]

9 23 ms 20 ms 21 ms ibx.ge-0-2-0.cr2.wdc1.speakeasy.net [206.223.115.4]

10 35 ms 36 ms 33 ms fe-0-3-3.cr2.chi1.speakeasy.net [69.17.83.41]

11 30 ms 28 ms 37 ms 69.12.89.6

 

Trace complete.

 

---------------------------------------------------------------

 

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 gnome.domain_not_set.invalid [68.76.106.112]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1

0/ 100 = 0% |

2 12ms 0/ 100 = 0% 0/ 100 = 0% adsl-68-76-111-254.dsl.bcvloh.ameritech.net [68.76.111.254]

0/ 100 = 0% |

3 13ms 0/ 100 = 0% 0/ 100 = 0% dist1-vlan50.bcvloh.sbcglobal.net [66.73.20.226]

0/ 100 = 0% |

4 11ms 0/ 100 = 0% 0/ 100 = 0% bb2-g2-3-0.bcvloh.sbcglobal.net [66.73.20.100]

0/ 100 = 0% |

5 13ms 1/ 100 = 1% 1/ 100 = 1% core1-p5-3.crcloh.sbcglobal.net [151.164.41.195]

0/ 100 = 0% |

6 22ms 0/ 100 = 0% 0/ 100 = 0% core1-p3-0.crhnva.sbcglobal.net [151.164.240.122]

0/ 100 = 0% |

7 21ms 0/ 100 = 0% 0/ 100 = 0% bb1-p5-0.hrndva.sbcglobal.net [151.164.242.70]

0/ 100 = 0% |

8 23ms 0/ 100 = 0% 0/ 100 = 0% ex1-p11-0.eqabva.sbcglobal.net [151.164.40.49]

0/ 100 = 0% |

9 --- 100/ 100 =100% 100/ 100 =100% ibx.ge-0-2-0.cr2.wdc1.speakeasy.net [206.223.115.4]

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% fe-0-3-3.cr2.chi1.speakeasy.net [69.17.83.41]

0/ 100 = 0% |

11 30ms 0/ 100 = 0% 0/ 100 = 0% 69.12.89.6

 

Trace complete.

 

an as you can see here loss of 100% 5 mins later with pathping

 

I dont even hit the L3 servers, thats a problem with you mid/central west people?

Edited by inexion
Link to comment
Share on other sites

ok I ran that tracert test thingy but I don't know what the results mean, can someone help?

 

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 * * * Request timed out.

2 8 ms 15 ms 9 ms ge-1-22-ur01.arlington.va.bad.comcast.net [68.87.129.225]

3 10 ms 8 ms 13 ms te-9-3-ur02.alexandria.va.bad.comcast.net [68.87.128.141]

4 19 ms 21 ms 12 ms te-9-1-ur01.alexandria.va.bad.comcast.net [68.87.128.133]

5 23 ms 9 ms 9 ms te-8-1-ur01.capitolhghts.md.bad.comcast.net [68.87.128.138]

6 11 ms 11 ms 10 ms te-8-1-ur02.capitolhghts.md.bad.comcast.net [68.87.129.150]

7 9 ms 9 ms 10 ms te-9-2-ar01.capitolhghts.md.bad.comcast.net [68.87.129.145]

8 16 ms 13 ms 13 ms po10-ar01.whitemarsh.md.bad.comcast.net[68.87.129.138]

9 12 ms 14 ms 11 ms 68.87.16.137

10 22 ms 51 ms 19 ms 12.118.149.13

11 18 ms 28 ms 19 ms tbr1-p010501.n54ny.ip.att.net [12.123.3.10]

12 16 ms 17 ms 17 ms ggr2-p300.n54ny.ip.att.net [12.123.3.58]

13 23 ms 24 ms 24 ms so-1-3-0.gar4.NewYork1.Level3.net [4.68.127.149]

14 22 ms 64 ms 20 ms ae-1-54.bbr2.NewYork1.Level3.net [4.68.97.97]

15 47 ms 35 ms 41 ms ae-0-0.bbr2.Chicago1.Level3.net [64.159.1.34]

16 36 ms 37 ms 40 ms ge-6-2.ipcolo2.Chicago1.Level3.net [4.68.101.137]

17 45 ms 38 ms 37 ms unknown.Level3.net [166.90.208.206]

18 38 ms 48 ms 37 ms 69.12.89.6

 

Trace complete.

Link to comment
Share on other sites

Lol this has been up for two days and no replys, I guess no one can help me. I do notice that the first server times out and it had to route through 18 servers which is 8 more than I see on almost everyone else's. So maybe that is my problem. I figured I would have good connections here in D.C. Isn't there that backbone thingy somewhere near me???

Link to comment
Share on other sites

C:\Documents and Settings\VooDoo>tracert 69.12.89.6

 

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 1 ms 1 ms 1 ms 192.168.0.1

2 8 ms 8 ms 9 ms 10.60.32.1

3 8 ms 11 ms 12 ms fas4-2.fmhlmi1-rtr2.twmi.rr.com [24.169.225.109]

 

4 9 ms 50 ms 9 ms pos0-3.lvnami1-rtr2.twmi.rr.com [24.169.225.74]

 

5 19 ms 17 ms 19 ms son1-0-0.mtgmoh1-rtr0.columbus.rr.com [65.25.128

.153]

6 30 ms 34 ms 32 ms son3-0-2.ncntoh1-rtr0.neo.rr.com [65.25.128.209]

 

7 40 ms 40 ms 39 ms so-2-1-0-0.gar1.Chicago1.Level3.net [67.72.120.1

]

8 38 ms 45 ms 39 ms so-3-3-0.bbr2.Chicago1.Level3.net [4.68.96.49]

9 41 ms 39 ms 38 ms ge-6-2.ipcolo2.Chicago1.Level3.net [4.68.101.137

]

10 38 ms 48 ms 39 ms unknown.Level3.net [166.90.208.206]

11 41 ms 41 ms 41 ms 69.12.89.6

 

Trace complete.

 

Can someone read my numbers and tell me my fortune? :unsure:

Link to comment
Share on other sites

You can tell very little from your tracert other than your hops, and average pings through them. If you want to know your packet loss percentage then download the free version of ping plotter. After running that program I am finding that I have a really cruddy internet connection with loss at about every hop all the way from my computer to the game server.

 

You're fortune: I see a download in your future. A small download, but one that will change the way you look at internet gamming for the rest of your life. Or a pizza delivery...mmmm pizza.

Link to comment
Share on other sites

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\Jones>tracert 69.12.89.6

 

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

1 1 ms <1 ms <1 ms 192.168.2.1

2 23 ms 26 ms 7 ms 10.229.56.1

3 17 ms 22 ms 13 ms 68.87.177.109

4 23 ms 29 ms 9 ms 68.87.174.33

5 9 ms 8 ms 7 ms 68.87.174.29

6 8 ms 13 ms 17 ms 68.87.174.25

7 14 ms 16 ms 20 ms 68.87.174.21

8 24 ms 62 ms 51 ms 12.118.239.169

9 30 ms 44 ms 30 ms tbr1-p012301.cgcil.ip.att.net [12.123.6.9]

10 25 ms 28 ms 23 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65]

11 24 ms 24 ms 29 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77

]

12 25 ms 30 ms * so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

 

13 85 ms 114 ms 171 ms ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

 

14 68 ms 63 ms 59 ms unknown.Level3.net [166.90.208.206]

15 26 ms 25 ms 41 ms 69.12.89.6

 

Trace complete.

 

C:\Documents and Settings\Jones>tracert 69.12.89.6.

 

Tracing route to 69.12.89.6. [69.12.89.6]

over a maximum of 30 hops:

 

1 1 ms 2 ms 2 ms 192.168.2.1

2 21 ms 17 ms 24 ms 10.229.56.1

3 13 ms 21 ms 12 ms 68.87.177.109

4 8 ms 12 ms 9 ms 68.87.174.33

5 10 ms 9 ms 22 ms 68.87.174.29

6 20 ms 21 ms 9 ms 68.87.174.25

7 543 ms 217 ms 40 ms 68.87.174.21

8 288 ms 29 ms 37 ms 12.118.239.169

9 66 ms 25 ms 28 ms tbr1-p012301.cgcil.ip.att.net [12.123.6.9]

10 27 ms 24 ms 27 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65]

11 200 ms 171 ms 40 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77

]

12 253 ms 190 ms 220 ms so-2-1-0.bbr1.Chicago1.Level3.net [209.244.8.9]

 

13 384 ms 242 ms 110 ms ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

 

14 34 ms 28 ms 26 ms unknown.Level3.net [166.90.208.206]

15 331 ms 325 ms 30 ms 69.12.89.6

 

Trace complete.

 

C:\Documents and Settings\Jones>tracert 69.12.89.6.

 

Tracing route to 69.12.89.6. [69.12.89.6]

over a maximum of 30 hops:

 

1 <1 ms <1 ms 1 ms 192.168.2.1

2 9 ms 8 ms 7 ms 10.229.56.1

3 8 ms 9 ms 8 ms 68.87.177.109

4 8 ms 9 ms 8 ms 68.87.174.33

5 8 ms 11 ms 10 ms 68.87.174.29

6 9 ms 10 ms 8 ms 68.87.174.25

7 9 ms 7 ms 8 ms 68.87.174.21

8 24 ms 29 ms 25 ms 12.118.239.169

9 24 ms 26 ms 27 ms tbr1-p012301.cgcil.ip.att.net [12.123.6.9]

10 23 ms 23 ms 23 ms ggr2-p310.cgcil.ip.att.net [12.123.6.65]

11 25 ms 24 ms 25 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77

]

12 24 ms 23 ms * so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

 

13 27 ms 25 ms 25 ms ge-6-1.ipcolo2.Chicago1.Level3.net [4.68.101.73]

 

14 23 ms 24 ms 27 ms unknown.Level3.net [166.90.208.206]

15 26 ms 25 ms 25 ms 69.12.89.6

 

Trace complete.

 

C:\Documents and Settings\Jones>pathping 69.12.89.6

 

Tracing route to 69.12.89.6 over a maximum of 30 hops

 

0 asdf-zriaub2e3f.MSHOME [192.168.2.39]

1 192.168.2.1

2 10.229.56.1

3 68.87.177.109

4 68.87.174.33

5 68.87.174.29

6 68.87.174.25

7 68.87.174.21

8 12.118.239.169

9 tbr1-p012301.cgcil.ip.att.net [12.123.6.9]

10 ggr2-p310.cgcil.ip.att.net [12.123.6.65]

11 so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77]

12 so-2-1-0.bbr2.Chicago1.Level3.net [209.244.8.13]

13 ge-6-0.ipcolo2.Chicago1.Level3.net [4.68.101.9]

14 unknown.Level3.net [166.90.208.206]

15 69.12.89.6

 

Computing statistics for 375 seconds...

Source to Here This Node/Link

Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

0 asdf-zriaub2e3f.MSHOME [192.168.2.

39]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1

0/ 100 = 0% |

2 8ms 0/ 100 = 0% 0/ 100 = 0% 10.229.56.1

0/ 100 = 0% |

3 9ms 0/ 100 = 0% 0/ 100 = 0% 68.87.177.109

0/ 100 = 0% |

4 9ms 0/ 100 = 0% 0/ 100 = 0% 68.87.174.33

0/ 100 = 0% |

5 9ms 0/ 100 = 0% 0/ 100 = 0% 68.87.174.29

0/ 100 = 0% |

6 9ms 0/ 100 = 0% 0/ 100 = 0% 68.87.174.25

0/ 100 = 0% |

7 12ms 0/ 100 = 0% 0/ 100 = 0% 68.87.174.21

0/ 100 = 0% |

8 25ms 0/ 100 = 0% 0/ 100 = 0% 12.118.239.169

0/ 100 = 0% |

9 --- 100/ 100 =100% 100/ 100 =100% tbr1-p012301.cgcil.ip.att.net [12.

123.6.9]

0/ 100 = 0% |

10 --- 100/ 100 =100% 100/ 100 =100% ggr2-p310.cgcil.ip.att.net [12.123

.6.65]

0/ 100 = 0% |

11 28ms 0/ 100 = 0% 0/ 100 = 0% so-1-1-0.edge1.Chicago1.Level3.net

[209.0.227.77]

0/ 100 = 0% |

12 27ms 0/ 100 = 0% 0/ 100 = 0% so-2-1-0.bbr2.Chicago1.Level3.net

[209.244.8.13]

0/ 100 = 0% |

13 25ms 0/ 100 = 0% 0/ 100 = 0% ge-6-0.ipcolo2.Chicago1.Level3.net

[4.68.101.9]

0/ 100 = 0% |

14 --- 100/ 100 =100% 100/ 100 =100% unknown.Level3.net [166.90.208.206

]

0/ 100 = 0% |

15 26ms 0/ 100 = 0% 0/ 100 = 0% 69.12.89.6

 

Trace complete.

 

C:\Documents and Settings\Jones>

Link to comment
Share on other sites

Brillow and Ice, do me a favor...run a plot directly to that troubled router.

 

Here's mine showing zero loss:

 

chilevel3.png

 

It will be interesting to see your results. If it pings clean, then there's a routing issue as far as this router is concerned with it's forwarding or something. The more information I have, the more I can take to someone who perhaps can look into it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...