Trace File

[LA_MERC_Andyconda]

After our BF2 server crashed I couldn't reconnect to it while others could. Here's the trace file I ran after it happened. What does this tell me.

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

F:\>tracert 74.232.68.74

Tracing route to adsl-232-68-74.asm.bellsouth.net [74.232.68.74]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.1.1
2 8 ms * 7 ms 68.152.190.226
3 8 ms 9 ms 5 ms 68.208.253.145
4 16 ms 15 ms 16 ms ixc00mob-ge-0-0-1.bellsouth.net [205.152.191.81]

5 14 ms 12 ms 11 ms axr00mgm-so-0-1-0.bellsouth.net [65.83.239.80]
6 14 ms 12 ms 13 ms axr01mgm-ge-0-0-0.bellsouth.net [65.83.238.27]
7 16 ms 16 ms 16 ms axr00aep-so-2-0-0.bellsouth.net [65.83.236.38]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

[LA_MERC_DocSparky]

I'm not real familiar with the Bellsouth router names, but it looks like a peering problem. The connection from Bellsouth to the next guy was down. It's hard to tell whether that is the last hop before the outside world though. Rerun the tracert to see what path the packets are taking and what comes after axr00aep-so-2-0-0.bellsouth.net (if the same route is taken). Generally, you can complain to Bellsouth but I doubt it will do any good.

We've got to have some better info than this out there. Anybody else want to take a shot?

[Rollout]

Hey I've heard about those peeing problems, you can fix that with a Depends Andy. Just pick some up on the way home and we'll see you on later this evening!!! :)

[LA_MERC_YellowDog]

I ran the same TraceRT... last night for comparison to yours...

Heres what I got.




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

C:\Documents and Settings\YellowDog>tracert 72.232.68.74

Tracing route to 74.68.232.72.static.reverse.layeredtech.com [72.232.68.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 47 ms 10 ms 10.105.64.1
3 11 ms 12 ms 13 ms 24.31.196.249
4 16 ms 34 ms 14 ms srp4-0.clmascmhe-rtr2.sc.rr.com [24.31.193.130]

5 17 ms 21 ms 19 ms 24.93.64.62
6 30 ms 57 ms 18 ms pop1-cha-P2-0.atdn.net [66.185.138.77]
7 88 ms 78 ms 203 ms bb1-cha-P3-0.atdn.net [66.185.138.64]
8 23 ms 23 ms 20 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
9 24 ms 33 ms 45 ms pop1-atm-P1-0.atdn.net [66.185.147.193]
10 65 ms 42 ms 45 ms savvis.atdn.net [66.185.150.14]
11 * 51 ms 45 ms cr2-loopback.ald.savvis.net [208.172.66.71]
12 45 ms 76 ms 38 ms dcr2-so-2-0-0.dallas.savvis.net [204.70.192.70]

13 49 ms 40 ms 39 ms dcr1-so-6-0-0.dallas.savvis.net [204.70.192.49]

14 205 ms 39 ms 75 ms bhr1-pos-12-0.fortworthda1.savvis.net [208.172.1
31.82]
15 50 ms 49 ms 83 ms 216.39.66.30
16 * 60 ms * 216.39.66.30
17 * * 55 ms 74.68.232.72.static.reverse.layeredtech.com [72.
232.68.74]

Trace complete.

C:\Documents and Settings\YellowDog>


Dont, know what the * are all about.. but there is a lot it seems going on to get me to the server.

[LA_MERC_DocSparky]

Your tracert doesn't really help Andy figure out what's up with Bellsouth, but it shows some packet loss at or very close to the server host. The *s indicate that there wasn't a response to the packet. There are three test for each node along the tracert. If I remember correctly we would all typically have a connection lost message at the same. That is probably due to packet loss at the host.

I think I'll run a few tracerts tonight if someone is on there. If someone has a decent network analysis tool (tracert is pretty basic stuff), then see if you can find out what the deal is with the server host.