116 replies to this topic

[Why Two Kay]

IF you read the WHOLE thread you would see he is from CS.

Grrr......quit posting after me, I know that, but others may not (or are too lazy to) so I decicded to post that so we dont get people coming in and saying "it didnt work whynot huh!!!"

[@n@rchist]

Grrr......quit posting after me

um...no

[[USAF]FiGhTaPiLOt]

Well, it took them just a little over a week, but somewhere in TX those llamas fixed the router I was going through (ir whatever else the problem was) and my lag finally chilled out this past evening. Even this afternoon, the lag was horrible, but now its ok. Thanks to all for your time and effort(s).

[Enforcer]

See we told you it was out of your control, that is was not your stuff but someone else's. Moongamers tech support. That'll be $50 please.

[[USAF]FiGhTaPiLOt]

ROFL, what if I maybe make a donation sometime...

[Spastic Colon]

See we told you it was out of your control, that is was not your stuff but someone else's. Moongamers tech support. That'll be $50 please.

Enforcer, don't you know your supposed to ask for their CC # at the BEGINNING of the call?

Amature!

[LITUP]

just a test...sorry to interrupt

[[USAF]FiGhTaPiLOt]

Everyone is lagging big time on the server right now.

[Lin]

Should be ok now.

[Cannon Fodder]

Fighta, have you tried running HiJack This? It tells you everything that is running on your system. You have to know how to read it, but if you don't, we have people who do.

Let's keep working on this!

Is that a worthwhile program?

[Afrika Korps]

Tracing route to 38.113.32.216 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 50 ms 49 ms 50 ms 65-255-64-1.dyn.adsl.pldi.net [65.255.64.1]
3 50 ms 51 ms 50 ms waltgw-fas0-0.pldi.net [64.250.192.1]
4 63 ms 69 ms 60 ms 500.Serial1-2.GW5.DFW7.ALTER.NET [157.130.135.57
]
5 62 ms 61 ms 62 ms 0.so-5-1-0.XL1.DFW13.ALTER.NET [152.63.101.34]
6 62 ms 69 ms 69 ms 0.so-3-1-0.XL1.DFW9.ALTER.NET [152.63.103.217]
7 63 ms 66 ms 69 ms 0.so-6-0-0.BR6.DFW9.ALTER.NET [152.63.99.2]
8 64 ms 68 ms 68 ms 204.255.173.6
9 67 ms 67 ms 64 ms p11-0.core02.dfw01.atlas.cogentco.com [154.54.2.
193]
10 75 ms 73 ms 74 ms p15-0.core01.mci01.atlas.cogentco.com [66.28.4.3
8]
11 75 ms 74 ms 79 ms 6T-1EV.demarc.cogentco.com [66.28.21.186]
12 *


Please help I used to have a ping of 35 and now its 100+!!

[Why Two Kay]

Its a problem at Cogentco, not your system, try a reverse ping.

Edit: Seems to be down.....

[Lin]

Wow...35 ping...all the way from South Afrika...


sooooo busted!

[Why Two Kay]

Wow...35 ping...all the way from South Afrika...


sooooo busted!

Ohhhhhhhhhhhhhhhhhhhhhhh

[Afrika Korps]

I try to keep myself at an un-disclosed locatoion due to my father working at the NSA.
Whups! I'll have to kill everyone now.
But really, could I have some help? And I have no idea what a reverse ping is...

[BrEEd]

My Ping just started to go dead on me. I have reset the router, did a defrag, dick clean-up, and spyware search...nothing working. So...

My IP-to-Server:
Tracing route to 38.113.32.216 over a maximum of 30 hops

1 2 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 8 ms 10.0.0.1
3 6 ms 7 ms 7 ms host-24-225-237-233.patmedia.net [24.225.237.233
]
4 9 ms 7 ms 8 ms host-24-225-237-226.patmedia.net [24.225.237.226
]
5 13 ms 11 ms 12 ms 12.119.53.69
6 267 ms 272 ms 282 ms tbr2-p012401.phlpa.ip.att.net [12.123.137.49]
7 273 ms 268 ms 277 ms tbr1-cl9.wswdc.ip.att.net [12.122.2.85]
8 271 ms 265 ms 264 ms ggr2-p300.wswdc.ip.att.net [12.123.9.81]
9 273 ms 276 ms 272 ms att-gw.dc.cogent.net [192.205.32.86]
10 262 ms 253 ms 266 ms p11-0.core02.dca01.atlas.cogentco.com [154.54.2.
197]
11 279 ms 285 ms 293 ms p6-0.core01.jfk02.atlas.cogentco.com [66.28.4.82
]
12 288 ms 294 ms 299 ms p15-0.core02.jfk02.atlas.cogentco.com [66.28.4.1
4]
13 43 ms 39 ms 38 ms p14-0.core02.ord01.atlas.cogentco.com [66.28.4.8
6]
14 325 ms 333 ms 340 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
15 332 ms 315 ms 328 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 * * * 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.


Server-to-IP:
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 15 ms <10 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37]

4 16 ms 16 ms 15 ms att.dfw01.atlas.cogentco.com [154.54.10.142]

5 <10 ms 16 ms 15 ms tbr2-p012302.dlstx.ip.att.net [12.123.16.246]

6 15 ms 32 ms 15 ms tbr2-cl6.sl9mo.ip.att.net [12.122.10.89]

7 31 ms 47 ms 32 ms tbr1-cl2.sl9mo.ip.att.net [12.122.9.141]

8 47 ms 47 ms 46 ms 12.122.12.185

9 47 ms 47 ms 62 ms tbr2-cl1.phlpa.ip.att.net [12.122.10.38]

10 47 ms 63 ms 47 ms gbr2-p30.phlpa.ip.att.net [12.122.12.110]

11 46 ms 47 ms 47 ms gar1-p370.phlpa.ip.att.net [12.123.137.25]

12 281 ms 297 ms 266 ms 12.118.191.106

13 313 ms 312 ms 329 ms host-24-225-192-144.patmedia.net [24.225.192.144]

14 297 ms 312 ms 313 ms host-24-225-237-234.patmedia.net [24.225.237.234]

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.

[SLow POke]

BadAssPenquin

There's congestion between hops 5 and 6 of your trace route. Nothing you can do about it. Suspect its congestion.

5 13 ms 11 ms 12 ms 12.119.53.69
6 267 ms 272 ms 282 ms tbr2-p012401.phlpa.ip.att.net [12.123.137.49]

16 through 30 hops are because of ping (person in need of graduation or ICMP echo)
are being rejected by a firewall on a server or router.

When pings start going south it's a good indication the network isn't feeling so good.
More often it's the start of something awful like a major carrier failure or congestion.

There's some tweaks like changing your TCP window size to maximize your bandwidth and computer memory (see transmit and receiver buffers).

And then, some pings will work but after a while don't. This could be a result of an automated filter that believes there's a denial of service attack using ping's of "death".

Here are some tools to use to trace from other locations.

>>>> http://www.traceroute.org/ looking glass project is so useful

VisualRoute is the total cool thing to have if you can afford it.

>>>> http://visualroute.visualware.com/


Remember, the network is a fickle. It would turn ugly at a drop of a hat due to all sorts of reasons. Yes, it can be frustration for a user, but you’re not the only one who’s head is denting the keyboard.

[Private Skippy]

If I can add one more link: Internet Health Report

Here you can see what's going on out in the clouds and even drill down into the different providers' POPs. Kinda cool in a geeky sort of way, but if you are having ping issues or just general internet slowage, this is a good place to start.

[SLow POke]

Excellent link Skippy!

Much better than that nasty MRTG *multi router traffic grapher

http://people.ee.eth.../webtools/mrtg/

[Pinkerton]

lmao,