Thread: Tracert's

hmmm.

well. the hypernia box for BF2 is where the source box is. The L4D box is also hypernia, but in a different data center. And the ArmA box is also in a different data center, AND with a different host.

Also, trace the AA3 IP. That's gameservers.com....and they're just as legit and high end as hypernia.

trace em all.

Originally Posted by ...bigdog...

hmmm.

well. the hypernia box for BF2 is where the source box is. The L4D box is also hypernia, but in a different data center. And the ArmA box is also in a different data center, AND with a different host.

Also, trace the AA3 IP. That's gameservers.com....and they're just as legit and high end as hypernia.

trace em all.

_________________________________________________


http://www.texasteamplayers.com/gall...09_9_37_23.jpg

Traced L4D, ArmAII, & AA3. Different results. No *'s at all, which is what I'm used to seeing.

Braddoc had a little mini-guide (need to tell him to make it an article, I do) on how to pinpoint the trouble spot. It should be in here a few pages back, but the gist is to run a tracert and then ping each hop along the way to the servers with 200 low impact packets to see if you're experiencing loss along the way. walks off to PM Braddoc

The point is, if it were on my end then I would be getting little *'s no matter where I did a trace route to. I did these other three without a problem. Also, I just double checked the BF2/PR IP's yet again, with the same result. I have no reason to believe it's on my end. Not trying to be rude at all White, but I'm just a wee tad bit frustrated that the game servers I need to be on are somehow out of whack. I've done everything I could on my end, to no avail.

well.....it JUST SO HAPPENS that the BF2 and PR IP's will be changing to the L4D IP's ON MONDAY (sshhhhhh).

so....your problem will be solved then....given that your traces to the L4D IP's are clean. right?

Originally Posted by ...bigdog...

well.....it JUST SO HAPPENS that the BF2 and PR IP's will be changing to the L4D IP's ON MONDAY (sshhhhhh).

so....your problem will be solved then....given that your traces to the L4D IP's are clean. right?

One would most certainly hope so. It's makes it very hard to lead a squad/lead a team when I am driving, flying, or running around, and then I have to tell my guys to hold on because I'm temporarily disconnected and hope that they hear me.

Errr, disregard. The problem appears to have fixed itself. Lovely.

Looks like a vast improvement and a shorter route. Can't wait to give it a try. :10

OLD 2142 SERVER IP

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 14 ms 14 ms bras29-l0.pltnca.sbcglobal.net [151.164.184.109]

3 19 ms 18 ms 14 ms 76.246.22.1
4 13 ms 12 ms 13 ms bb1-g15-0.pltnca.sbcglobal.net [151.164.93.231]

5 13 ms 14 ms 13 ms 69.220.8.41
6 13 ms 13 ms 13 ms asn3356-level3.eqsjca.sbcglobal.net [151.164.250
.138]
7 18 ms 17 ms 17 ms vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
8 16 ms 16 ms 16 ms ae-93-93.ebr3.SanJose1.Level3.net [4.69.134.237]

9 37 ms 34 ms 36 ms ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
10 24 ms 34 ms 35 ms ae-92-98.ebr2.LosAngeles1.Level3.net [4.69.146.2
7]
11 67 ms 57 ms 68 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
12 56 ms 57 ms 56 ms ae-2-70.edge3.Dallas1.Level3.net [4.69.145.72]
13 57 ms 58 ms 56 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6
]
14 56 ms 58 ms 56 ms 66.18.0.142.databank.com [66.18.0.142]
15 * * * Request timed out.
16 * * * Request timed out.
17 57 ms 57 ms 58 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

NEW 2142 SERVER IP

Tracing route to unknown.dfw.colocrossing.com [207.210.254.226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 15 ms 14 ms bras29-l0.pltnca.sbcglobal.net [151.164.184.109]

3 13 ms 12 ms 12 ms 76.246.22.1
4 12 ms 12 ms 12 ms bb1-10g2-0.pltnca.sbcglobal.net [151.164.42.100]

5 13 ms 14 ms 13 ms ex2-p10-0.pxpaca.sbcglobal.net [151.164.190.83]

6 15 ms 23 ms 13 ms as4323-twtelecom.pxpaca.sbcglobal.net [151.164.2
48.110]
7 56 ms 55 ms 55 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.
234.20]
8 56 ms 55 ms 56 ms 206.123.64.34
9 57 ms 56 ms 58 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]

10 56 ms 57 ms 57 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

You may need to post during the lag spikes. Could be an overloaded router during peak usage.