116 replies to this topic

[Akooma]

To Trace from your IP to our Servers:

1-Please write down your IP <Click Here if you don't know your IP>

2-Click the [Start] menu and select the Run option.

3-Type Command in the run bar and press enter. A dos box should appear.

4-Type the following at the command prompt- tracert 38.113.32.216 and press the [Enter] key. Your computer should now start trace routing to the Omaha Classic server. (38.113.32.195 - CS:Source, HL2DM, DoD) (38.113.32.165 - BFV, BF mods) (67.15.23.177 Moon Playground)

5-Once the traceroute is complete, right click on the Dos box and choose Select All from the popup menu. The whole Dos box should hi-lite.

6-Hold down the Ctrl key and press C. You should now have a copy of the trace on your clipboard.

7-You can close the Dos box by typing exit at the dos prompt and hitting the [Enter] key.

8-Post the results here or just email me ( [email protected] ) and we will try and rectify the issue. Keep in mind that if you notice a change in ping quality, you can be helped. If your ping was hopeless to begin with don't bother. It is on your end.


To Trace from our Servers to your IP:


1-Please write down your IP <Click Here if you don't know your IP>

2-Use the following link and enter your ip in the provided ip address entry box and hit the [TraceIP] button <Click Me>

3-Post the results here (cut, copy, and paste) or just email me ( [email protected] ) and we will try and rectify the issue. Keep in mind that if you notice a change in ping quality, you can be helped. If your ping was hopeless to begin with don't bother. It is on your end.



Summary:

-Both traces should be performed prior to asking for help. If the trace is fine from the servers to your IP but messed up from your IP to the Servers (or vice versa), the routing may be borked.

-If Both traces show similar resuts, there is probably an issue with one of the routers. Post here or email me and I will pass the information along to the bandwidth provider.

[Cannon Fodder]

Well, it did it again...and here's the results...

Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\CHRISH~1>tracert 38.113.32.216

Tracing route to 38.113.32.216 over a maximum of 30 hops

1 7 ms 7 ms 7 ms 10.94.176.1
2 10 ms 8 ms 7 ms 172.30.50.145
3 8 ms 8 ms 8 ms 172.30.50.186
4 10 ms 7 ms 7 ms 68.52.0.50
5 16 ms 16 ms 15 ms 12.124.65.53
6 15 ms 17 ms 16 ms gbr5-p90.attga.ip.att.net [12.123.21.82]
7 17 ms 18 ms 17 ms tbr1-p013501.attga.ip.att.net [12.122.12.21]
8 29 ms 30 ms 30 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
9 31 ms 29 ms 29 ms ggr2-p3120.wswdc.ip.att.net [12.123.9.117]
10 30 ms 31 ms 30 ms att-gw.dc.cogent.net [192.205.32.86]
11 31 ms 31 ms 29 ms p11-0.core02.dca01.atlas.cogentco.com [154.54.2.
197]
12 37 ms 40 ms 41 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82
]
13 35 ms 36 ms 38 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
4]
14 51 ms 56 ms 50 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.8
6]
15 188 ms 172 ms 189 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
16 175 ms 180 ms 186 ms g49.ba01.b005948-0.mci01.atlas.cogentco.com [66.
28.5.90]
17 175 ms 182 ms 177 ms 6T-1EV.demarc.cogentco.com [66.28.21.186]
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 ^C

That's from my comp to the server. Here's from the server to my comp...

Tracing route to pcp02131138pcs.galitn01.tn.comcast.net [68.52.62.101]

over a maximum of 30 hops:



1 <10 ms <10 ms <10 ms 66.28.71.17

2 <10 ms <10 ms <10 ms f1.ba01.b005948-0.mci01.atlas.cogentco.com [66.28.21.185]

3 <10 ms <10 ms <10 ms g0-1.core01.mci01.atlas.cogentco.com [66.28.5.89]

4 <10 ms 15 ms

it locks up after #4 and doesn't add anything else.

help...want to play on moon. Need back up...

[Akooma]

You are having trouble with the same IP I am having trouble with.

It is AT&T's routers in Texas. They are severely borked up.

AOD please get your people in order

I'll tell Brian(our BW provider) about it. It is hard to do anything from our end. I don't want to do TCP/IP 101 but I will say that packet switching depends on the routers switching them.

[Cannon Fodder]

Damn Texans...been a pain in my ass since the day I was born!

[Akooma]

Here is your normal tracert....notice the 5th hop is Dallas/FW ATT pop. Same hop I have trouble with.

When it stops at 4 it is 5 that is the issue and when tracing from your location it is the same way. It is always the hop after the spike.


1 <10 ms <10 ms <10 ms 66.28.71.17

2 <10 ms <10 ms <10 ms f1.ba01.b005948-0.mci01.atlas.cogentco.com [66.28.21.185]

3 <10 ms <10 ms <10 ms g0-1.core01.mci01.atlas.cogentco.com [66.28.5.89]

4 <10 ms 16 ms <10 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37]

5 <10 ms 16 ms 15 ms att.dfw01.atlas.cogentco.com [154.54.10.142]

6 <10 ms 16 ms 16 ms tbr1-p012201.dlstx.ip.att.net [12.123.16.242]

7 31 ms 47 ms 47 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]

8 31 ms 47 ms 47 ms gbr6-p40.attga.ip.att.net [12.122.12.46]

9 31 ms 47 ms 47 ms gar3-p370.attga.ip.att.net [12.123.21.85]

10 47 ms 47 ms 46 ms 12.124.65.54

11 47 ms 46 ms 47 ms 68.52.1.1

[Why Two Kay]

Actually of all people, I am the closest to where the Playground is located, and I het the best ping there! Except for Gra1 and his stupid sub-15 pings.......

[Cannon Fodder]

Any word yet on if this will get resolved soon?

[Linux]

Gosh! I am having the same problems as Chris. I cannot play decently at Moon servers. Here is my chart for when the server pings me:

1 <10 ms <10 ms <10 ms 66.28.71.17

2 <10 ms <10 ms <10 ms f1.ba01.b005948-0.mci01.atlas.cogentco.com [66.28.21.185]

3 <10 ms <10 ms <10 ms g0-1.core01.mci01.atlas.cogentco.com [66.28.5.89]

4 <10 ms 16 ms <10 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37]

5 234 ms 234 ms 235 ms att.dfw01.atlas.cogentco.com [154.54.10.142]

6 203 ms 235 ms 234 ms tbr2-p012302.dlstx.ip.att.net [12.123.16.246]

7 235 ms 250 ms 234 ms tbr2-cl6.sl9mo.ip.att.net [12.122.10.89]

8 235 ms 250 ms 250 ms tbr1-cl2.sl9mo.ip.att.net [12.122.9.141]

9 266 ms 266 ms 250 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]

10 250 ms 266 ms 250 ms gar5-p300.wswdc.ip.att.net [12.123.9.105]

11 235 ms 234 ms 234 ms 12.118.122.6

12 235 ms 250 ms 250 ms pos-0-0-cr01.whitemarsh.md.core.comcast.net [68.87.16.21]

13 235 ms 250 ms 234 ms pos-9-1-ar01.whitemarsh.md.md01.comcast.net [68.87.19.178]

14 234 ms 250 ms 235 ms ge-0-11-sr01.elkton.md.md01.comcast.net [68.87.56.254]

15 234 ms 266 ms 250 ms ge-4-1-sr01.dover.md.md01.comcast.net [68.87.56.250]

16 250 ms 265 ms 266 ms ge-0-11-sr01.harrington.md.md01.comcast.net [68.87.56.246]

17 266 ms 281 ms 281 ms ge-0-11-sr01.milford.md.md01.comcast.net [68.87.56.242]

18 265 ms 266 ms 281 ms fe-0-0-ubr01.milford.md.md01.comcast.net [68.87.56.98]

At ATT Dal/Fw it goes crazy. I just hope they get their problems fixed up.

[Akooma]

Don't worry fellas, it is being worked on.

Our provider gave a phone call to AT&T and Cogent today and raised some hell.

It's not just us. That is a major pop so everyone going through it suffers. I know, I know, it's no consolation, but there are others bitching about it in his forum so rest assured it will be fixed.

I keep seeing a rise in ping around peak time. Then it subsides late at night. I relayed (no pun) that info to our provider and he will be monitoring it.

TTYL and keep me updated.

Ak

[MeanMachine]

Akooma can you tell me if this is a BT (British Telecom UK) network issue of US Cogentco problem?


C:\Documents and Settings\Roger>tracert 38.113.32.216

Tracing route to 38.113.32.216 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 18 ms 14 ms 18 ms rasa1nrp5.ealing.broadband.bt.net [213.120.187.1
8]
4 18 ms 14 ms 14 ms 81.146.247.30
5 16 ms 15 ms 14 ms 217.41.168.1
6 15 ms 16 ms 14 ms 217.41.168.114
7 13 ms 13 ms 13 ms 217.41.168.34
8 155 ms 152 ms 151 ms 213.120.192.25
9 145 ms 145 ms 146 ms core2-pos4-1.ealing.ukcore.bt.net [194.72.9.217]

10 155 ms 158 ms 157 ms core2-pos5-0.telehouse.ukcore.bt.net [194.74.65.
181]
11 153 ms 153 ms 151 ms 195.66.224.185
12 237 ms 236 ms 235 ms p6-0.core02.jfk01.atlas.cogentco.com [154.54.1.5
]
13 234 ms 235 ms 227 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
69]
14 254 ms 257 ms 261 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.8
6]
15 262 ms 261 ms 260 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
16 266 ms 272 ms 269 ms 6T-1EV.demarc.cogentco.com [66.28.21.186]
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


Thanks,

Roger

[Why Two Kay]

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.

Its the Birtish thing because I get that Request Timed Out too, yet I ping only 30.

[commando]

83.109.252.68


thats all that poped up

[Akooma]

BF classic and CS will never respond to your ping. This is protection for our servers.

When you see the latency number jump it is most likely the hop before or the hop after.

It appears to jump in the UK and when it hits Cogentco as well. This could be due to the storm that's kicking everyone's butt in the midwest and east coast (not to mention you're coming from half way around the world).

Please click on our provider's link at the top of this thread and trace back to your IP address. Packets typically do not follow the same path as they came. So it is a two way street.

Also, what is your typical ping?


Thanks,

Jim

[MeanMachine]

Thanks Jim, it was almost back to normal by the time of the fest. Our ping is normally in the 140 range.

If this happens again I will make sure to trace both ways to get a complete picture.

[commando]

it worked better for me this time



Microsoft® Windows DOS
©Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\EIRIKS~1>tracert 38.113.32.216

Tracing route to 38.113.32.216 over a maximum of 30 hops

1 20 ms 27 ms 18 ms ti311110a080-l1.ti.telenor.net [80.212.144.0]
2 28 ms 26 ms 27 ms ti300722c050-ge2-0-12.ti.telenor.net [146.172.20
8.41]
3 28 ms 29 ms 29 ms ti300002c050-pos4-2.ti.telenor.net [146.172.252.
10]
4 26 ms 29 ms 26 ms ti300001c050-pos4-1.ti.telenor.net [146.172.248.
81]
5 28 ms 29 ms 26 ms ti200001c050-pos4-3.ti.telenor.net [146.172.248.
78]
6 28 ms 29 ms 29 ms ti100001c050-pos9-0.ti.telenor.net [146.172.248.
14]
7 25 ms 27 ms 25 ms ti100001b051-ge0-0.ti.telenor.net [146.172.248.9
4]
8 27 ms 26 ms 26 ms nb01b12-ge0-0.nb.telenor.net [217.70.229.65]
9 50 ms 49 ms 49 ms nb21b12-pos4-3.nb.telenor.net [217.70.227.22]
10 48 ms 50 ms 49 ms 195.66.226.185
11 119 ms 118 ms 118 ms p6-0.core02.jfk01.atlas.cogentco.com [154.54.1.5
]
12 120 ms 118 ms 118 ms p12-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
69]
13 145 ms 144 ms 144 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.8
6]
14 154 ms 155 ms 154 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
15 155 ms 158 ms 166 ms 6T-1EV.demarc.cogentco.com [66.28.21.186]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20













there ya go!

[commando]

could you plz help me with that?

[Lin]

commando, you're coming from Norway so your ping is unfortunately going to be high, always over 100 and probably much more.

Start watching what your ping is every time you enter the game, and write those down for a week. We need to know what your 'normal' ping is for the game, so we will know what should be considered 'abnormal'.

[commando]

normally its stabil at 145 - 155

[[USAF]FiGhTaPiLOt]

Hey Akooma, maybe you can help me...

I usually ping about 45-65 on any normal day. Funny thing is that I am still pinging in the 60's but everyone is teleporting around (like playing in a damn slide-show).

Here is the trace from my comp to the moon cs:s server:


Tracing route to 38.113.32.216 over a maximum of 30 hops

1 6 ms 5 ms 6 ms 10.117.108.1
2 12 ms 9 ms 9 ms 12.118.213.37
3 20 ms 17 ms 16 ms gbr6-p51.dlstx.ip.att.net [12.123.196.18]
4 17 ms 20 ms 17 ms tbr1-p012701.dlstx.ip.att.net [12.122.12.69]
5 18 ms 20 ms 18 ms ggr1-p360.dlstx.ip.att.net [12.123.16.241]
6 18 ms 18 ms 18 ms p12-3.core02.dfw01.atlas.psi.net [154.54.10.141]
7 26 ms 30 ms 28 ms p15-0.core01.mci01.atlas.cogentco.com [66.28.4.3
8]
8 44 ms 27 ms 26 ms 6T-1EV.demarc.cogentco.com [66.28.21.186]
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.


From the server to my comp seems to be all good:

Tracing route to 24-117-168-163.cpe.cableone.net [24.117.168.163]

over a maximum of 30 hops:


1 <10 ms <10 ms <10 ms 66.28.71.17
2 <10 ms <10 ms <10 ms f1.ba01.b005948-0.mci01.atlas.cogentco.com [66.28.21.185]
3 <10 ms 16 ms <10 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37]
4 <10 ms 16 ms <10 ms att.dfw01.atlas.cogentco.com [154.54.10.142]
5 <10 ms 15 ms 16 ms tbr2-p012302.dlstx.ip.att.net [12.123.16.246]
6 <10 ms 16 ms <10 ms gbr5-p40.dlstx.ip.att.net [12.122.12.86]
7 16 ms 15 ms 16 ms ar2-p310.ocyok.ip.att.net [12.123.196.9]
8 16 ms 16 ms 15 ms 12.118.213.38
9 15 ms 32 ms 31 ms 24-117-168-163.cpe.cableone.net [24.117.168.163]

Trace complete.


Guess the routing is b0rk3d. I need my daily fill of CS! Esp since I'm on leave and can play 24/7!!!

[Akooma]

Hmmm.....that traceroute looks fine to me.

This is why Don and I are working on ping checking/kicking.

No matter what your ping is if you are trying to kill someone who is lagging, you get the "teleport" effect. I presume a laggy player causes cpu spikes as well with all the retransmits the server has to make.