Thread: Tracert's

well, what bigdog said, just from my own inferences/assumptions from the trace....

that clustering of ip's in the "12's" (12.123..20.238, 12.122.2.89, etc.) all resolve to a domain name ending/belonging to at&t (*.att.net). and from that trace, the router that the ping shoots up starts at that last 12.119..136.18...since its the last "12", im just assuming that its at&t owned

anyhoo, since that last 12.x one has the 600 ping, then anyhting else behind it will have a similar ping. and since the 600 ping starts at that router, then something is fishy with that router, and since my assumption is that its a at&t, then thats why i say its their problem

also given that not everyone is/was having ping problems, indicates that its not anyhting that hte server can do. you can think of it like driving to a city (now i dont know anyhting about cities and texas, im just trying to make an analogy :P ), and consider each city a router/hub...

say mafia and digital are driving to dallas (the game server). both digital and mafia have been smooth sailing on nice 8 lane 70mph roads between each city (router), hardly any traffic and nice high speed limits. the last city that digital has to go through is houston before he goes straight to dallas, and mafia has to go through austin.

digital hits houston, still no traffic, and nice big 8 lane roads with a 70mph speedlimit, the rest of the way to dallas.

mafia on the other hand hits austin and something strange is going on for whatever reason...hits some traffic coming into teh city, and the roadway goes from that nice 8 lanes with the 70mph speed limit down to 2 lanes, maybe a little bumpy and the speedlimit throttled down to 30mph, the rest of the way to dallas.

and everyone else that takes the same route as mafia thru austin is going to hit that same lag on the way to dallas. while everyone that takes the same route as digital has those nice, fat, highspeed highways to dallas. but thats not to say that some other day houston could have some of that strangness going on, with hte fewer lanes of traffic and slower speed limit :P



dunno if that was the answer you were looking for or if you wanted any of that extra analogy stuff, but there ya go :P hope that helps

Originally Posted by ...bigdog...

PLEASE POST THE TEXT OF YOUR TRACERT, NOT A GOD DAMN SCREEN SHOT. THIS IS IN THE INSTRUCTIONS OF THE STICKY. HOW ARE WE SUPPOSED TO CUT AND PASTE THIS TO OUR ISP TECH'S? THEY DON'T TAKE PICTURES IN THEIR SUPPORT TICKETS.

jkl;asdfkljkls;adfjkjklasdrjkl;

[size=9px]Actually they do - you upload the file [/size] :?

Srry big - had to say it.

BUT WE ABSOLUTELY PREFER THEM IN TEXT!!!

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

H:\Documents and Settings\Joe>tracert 70.84.14.138

Tracing route to 138.70-84-14.kyronix.net [70.84.14.138]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 67.170.247.1
2 * * * Request timed out.
3 9 ms * 9 ms GE-1-1-ur01.fremont.ca.sfba.comcast.net [68.87.1
96.65]
4 9 ms * 10 ms 10g-9-1-ur02.fremont.ca.sfba.comcast.net [68.87.
192.62]
5 11 ms 11 ms * 10g-9-1-ur01.hayward.ca.sfba.comcast.net [68.87.
192.82]
6 8 ms 9 ms * 10g-9-1-ur02.hayward.ca.sfba.comcast.net [68.87.
192.86]
7 9 ms 9 ms * 10g-8-2-ar01.oakland.ca.sfba.comcast.net [68.87.
192.90]
8 12 ms 11 ms 11 ms 68.87.226.134
9 13 ms 13 ms 11 ms 68.86.90.81
10 16 ms 16 ms 16 ms te-0-0-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.84.42]
11 15 ms 15 ms 31 ms 64.215.30.201
12 57 ms 57 ms 57 ms The-Planet.ge-4-3-0.ar1.DAL2.gblx.net [64.210.10
4.58]
13 57 ms 69 ms 57 ms te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]

14 58 ms 57 ms 57 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

15 69 ms 58 ms 57 ms gi1-0-2.car13.dllstx4.theplanet.com [67.19.255.1
86]
16 58 ms 57 ms 57 ms 138.70-84-14.kyronix.net [70.84.14.138]

Trace complete.

H:\Documents and Settings\Joe>

well no wonder i couldn't stay connected to the server.