Request timed out issue.

Road Runner · Post by **Road Runner** » Fri Jun 17, 2011 2:15 am

You pinged Google.com with 5784 packets, but loss 6 packets in process, but it's really slim to none, in terms of packet loss, when you're looking at the number of packets sent / received.

Run trace route using the same cmd application with the command:

- tracert google.com

The tracert will show the number of hops (routers) it goes through to reach the destination server, which, in this case, is 74.125.93.104 (one of Google's servers). We should be able to pinpoint where the issue is at.

So go ahead and run the tracert, and post it here when you're done.

PS- make sure there's no applications in the background utilizing your bandwidth when testing.

nazralla · Post by **nazralla** » Fri Jun 17, 2011 9:48 am

Road Runner · Post by **Road Runner** » Fri Jun 17, 2011 3:34 pm

Your tracert looks OK to one of Google's servers at 74.125.93.147, but pings spike up at hop #7 - 72.14.233.87 -- but since Google has servers all over the country, I'm sure it's probably just a extra long hauls after it reaches #7, and continuing until it hits #11.

Just from the tracert you've posted, it doesn't look as Cox is the problem; it's after it leaves Cox's edge router, which is the "Internet Cloud".

However I'm more concerned with the WoW server- do you have an IP address available to test for latency? If so, try posting it here- an tracert and ping test (use command: ping -n 30 [insert WoW IP address here])

If things are still a bit out of whack, you can try changing your IP address so hopefully Cox will put you on a different subnet, thus putting you on a different route to the server; it's redundancy in case one route doesn't work.

nazralla · Post by **nazralla** » Fri Jun 17, 2011 7:45 pm

Road Runner · Post by **Road Runner** » Sat Jun 18, 2011 1:20 am

What happened to the ping command I asked you to run? You only have the tracert there.

And, I tried to run a tracert to the WoW server, but I know I'd have horrible gaming experience with the amount of hops I go through before I even get close to the gaming server:

Tracing route to 12.129.255.16 over a maximum of 30 hops

1 3 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 7 ms 7 ms 67.59.225.25
4 * * * Request timed out.
5 11 ms 11 ms 11 ms 64.15.2.178
6 12 ms 10 ms 11 ms xe-4-3-0.edge3.NewYork2.Level3.net [4.59.128.81]
7 12 ms 13 ms 11 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 12 ms 10 ms 11 ms ae-6-6.ebr2.NewYork1.Level3.net [4.69.141.21]
9 10 ms 17 ms 17 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

10 11 ms 11 ms 11 ms ae-3-89.edge3.NewYork1.Level3.net [4.68.16.145]

11 11 ms 11 ms 11 ms att-level3.newyork1.level3.net [4.68.63.142]
12 83 ms 81 ms 80 ms cr1.n54ny.ip.att.net [12.122.81.126]
13 81 ms 82 ms 82 ms cr2.cgcil.ip.att.net [12.122.1.2]
14 80 ms 81 ms 80 ms cr1.cgcil.ip.att.net [12.122.2.53]
15 78 ms 79 ms 79 ms cr2.dvmco.ip.att.net [12.122.31.85]
16 82 ms 81 ms 81 ms cr1.slkut.ip.att.net [12.122.30.25]
17 81 ms 81 ms 81 ms cr2.la2ca.ip.att.net [12.122.30.30]
18 82 ms 81 ms 81 ms gar4.lsrca.ip.att.net [12.122.104.89]
19 178 ms 210 ms 204 ms 12-122-254-230.attens.net [12.122.254.230]
20 81 ms 82 ms 81 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
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.

However, whatever spikes you're seeing with your connection appears to be beyond Cox's control and within the peer networks you're routing through. Now, can do you do anything about it? Probably not; but my only suggestion after this is the IP change trick I spoke about in my last post. I'm not 100% that it will change your routing, but I've seen others pull this off and things got better for whatever issues that were occurring. Now, just say you do get the IP changed and your routing changes in the first few hops, it may end going back to the same loop within the 'attens.net' networks.

Just some thoughts..

nazralla · Post by **nazralla** » Sat Jun 18, 2011 1:47 am

When I ping the server, all I got are requests timed out. I apprecaite you trying to help me. My friend did a few things when he came over earlier in the week that seem to have at least made it better. WoW is now playable. Before, I was being DCed and getting, so many lag spikes, I was considering quitting.

Road Runner · Post by **Road Runner** » Sun Jun 19, 2011 12:20 am

No problem, guy.

But, I'm curious to know- what exactly was your friend doing for hours to make it 'seem' faster in the end-game?

nazralla · Post by **nazralla** » Sun Jun 19, 2011 4:21 pm

There was a lot of noise in the signal, so he changed out all of the connecters and splitters, because they were all really old. Since then, I don't get randomly DCed or have as many lag spikes, but it does still exsist.