rage

**Bunni** · 10-02-12, 09:47 PM

Originally Posted by MeBad

1 * * * Request timed out.
2 6 ms 7 ms 7 ms tge7-2.snantx1400-er02.texas.rr.com [24.28.133.2
42]
3 14 ms 12 ms 11 ms tge8-1.snantx1400-er01.texas.rr.com [24.175.34.2
34]
4 19 ms 15 ms 15 ms tge0-8-0-9.snantx1000-tr01.texas.rr.com [24.175.
33.58]
5 16 ms 15 ms 15 ms 24.175.32.144
6 21 ms 38 ms 16 ms ae23.hstntxl3-rtr1.texas.rr.com [24.175.32.156]

7 30 ms 15 ms 15 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
8 15 ms 17 ms 15 ms ae-0-0.pr0.dfw10.tbone.rr.com [66.109.6.181]
9 16 ms 30 ms 17 ms 66.109.9.98
10 18 ms 17 ms 27 ms ae5.dar02.sr01.dal05.networklayer.com [173.192.1
8.217]
11 17 ms 21 ms 20 ms po2.fcr02.sr02.dal05.networklayer.com [173.192.1
18.141]
12 18 ms 17 ms 18 ms 91.90.173.184.hypernia.com [184.173.90.91]

Trace complete.

Any idea as to why mine times out when checking my router?

could be a setting on the router, wouldn't fret too much about it

**iLLusioN** · 10-02-12, 09:51 PM

Your router firewall is most likely just blocking ICMP packets. See if you can ping your router. If you don't know what IP that is or how to find it, open up command prompt and type in "ipconfig" You should be given 3 sets of numbers. The number listed for default gateway will be your home router. If you can't ping(example: ping 192.168.0.1) that then your router is blocking ICMP packets. I wouldn't worry about it if that's the case.

**MeBad** · 10-03-12, 07:05 PM

Thanks, I think that is def the issue. Forgot we got a new cable modem/wirless router combo from our ISP. Old one never did that.

**Rad** · 10-03-12, 07:37 PM

So nobody caught this line in his second post?

4 227 ms 27 ms 30 ms xe-0-3-0-0.core02.gf01.dllstx.grandecom.net [24.
155.121.86]

You shouldn't get those types of pings so close to your point of origin. I'm guessing something is wrong with your cable provider's network. Could be a switch, the head end, or a variety of things.

One thing you can try (but it doesn't always work very well since some devices will drop packets after numerous pings), ois to ping each individual address along the way to the server that is listed in your tracert. One of them will eventually spike.

That will tell you whether it's on your end or somewhere else. If every address spikes periodically then it's you.

You can also run a ping -t <ip of this server without the port) and just let it run. That will tell you if it's connection related or perhaps an in game setting. If the ping is spiking then your game settings will have minimal impact.

**enf** · 10-03-12, 08:14 PM

Or you can just blame all of your problems on our "shitty" servers...

**Guyver** · 10-03-12, 08:57 PM

Originally Posted by enf

Or you can just blame all of your problems on our "shitty" servers...

No, no...he said they're "garbage" not "shitty"....

Originally Posted by naerok

garbage servers, bad reg.. and horrible restart times with rubber banding... so is it the server company's servers? or what just want to know whats going on and what is happening to fix it. i have played on other servers that were amazing. or is it just my imagination? and me totally hating csgo.

**Stealthyking** · 10-03-12, 08:59 PM

Originally Posted by Guyver

No, no...he said they're "garbage" not "shitty"....

Yea, What he said. Get it right Enf.

**iLLusioN** · 10-03-12, 09:09 PM

Originally Posted by Rad

So nobody caught this line in his second post?

4 227 ms 27 ms 30 ms xe-0-3-0-0.core02.gf01.dllstx.grandecom.net [24.
155.121.86]

I did, which is why I asked if he still had issues with the lag. Spikes like that for a split second aren't too uncommon.

**Rad** · 10-03-12, 09:44 PM

I guess if you have a lackluster cable provider that would be considered uncommon, but that's on their own network before a hand-off. That really shouldn't be happening in my opinion.

**iLLusioN** · 10-03-12, 11:04 PM

There are about 2 million things that can cause a spike in ping for a second or 2 in a WAN environment. It's not uncommon. If it remained that way for more than 1-3 seconds or if that 1 second spike was happening consistently to a range of people, then you would have a problem. I deal with this crap all the time at work...somebody is troubleshooting a latency issue on the local network, they run a traceroute - and only one - see a higher than usual latency and immediately throw the trouble ticket up the networking ladder. 99% of the time it's nothing(and for once, that's not a made up statistic).