Tracert timed out, WTF?! HALP ME!!
Tracert timed out, WTF?! HALP ME!!
|
|
Dec 17 2007, 07:24 PM, updated 18y ago
Show posts by this member only | Post
#1
|
![]() ![]() ![]()
Junior Member
306 posts Joined: Jun 2005 From: Your closet |
I recently have serious issue with wow latency. Im getting 1000ms-1200ms frequently. The thing is my other friends in my area is able to connect smoothly. I can ping google.com and most international and local sites with good ping. Youtube and other streaming sites are perfectly fine. I went to Blizzard website and they asked me to run tracert on their "us.logon.worldofwarcraft.com" However, whenever i tried to run tracert on any sites to check my problem, i get timed out for all 30hops. (even tracert on tm website also timed out during tracert) Without the tracert reports, i couldnt send in any info to Blizz tech support. I called in 100 and f***ing streamyx just say the same thing. Reset port blah blah blah. I already switch off firewall and still tracert is giving timed out. Is it possible that Tm is trying to block tracert to prevent people from tracing bad routes? Can anyone with 124.82 ip range help me to run a tracert to "us.logon.worldofwarcraft.com" and post the results here? I suspect that Streamyx screw up the routing again. |
|
|
|
|
|
Dec 17 2007, 08:30 PM
Show posts by this member only | Post
#2
|
![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
1,846 posts Joined: Feb 2006 From: Kuching, Sarawak |
I connect usng 124.82 these days. Some connections get a lot of outside pings so I disconnect and redial back. I remember certain ranges f 124.82.xx or 124.82.xxx had really bad connections. Used to redial up until the connection was better but still not so good. Haven't raided in 2 weeks.
I can connct using 60.53 but even thatis not stable at night. Only morning time. Have you tried the VM solution? Planning to do that at home when I have time. Everydayis a stressful working day. Sigh. |
|
|
Dec 17 2007, 09:34 PM
Show posts by this member only | Post
#3
|
![]() ![]() ![]()
Junior Member
306 posts Joined: Jun 2005 From: Your closet |
Its the AT&T servers messing up.
I downloaded Pingplotter to trace route. Everything stops after it reaches attens server in US. Apparently, streamyx don't allow windows tracert to run. Heh, trying to cover up their bad routing. |
|
|
Dec 18 2007, 06:59 PM
Show posts by this member only | Post
#4
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
5,691 posts Joined: Mar 2006 |
Haha that's funny, cos their tech support still asks you to provide a tracert to the "problem ip" if you log a complaint.
Anyway I use WinMTR, it's a good tracert replacement. I've found that recently, pings to wow logon server was 400ms, but my in-game ping was 1200-2000. Turns out now my pings are OK, but the bandwidth is pure shit, so I had to turn off all my torrents to get 600-700ms in-game. |
|
|
Dec 18 2007, 11:23 PM
Show posts by this member only | Post
#5
|
![]() ![]()
Junior Member
257 posts Joined: Jun 2005 |
recently i notice about that too..
IP address hunting nowadays just dont work anymore.. I have vary result EACH WEEK, if not, can said EVERYDAY, not matter 218, 60.50, 60.52, 60.53 or worst 60.48 or 60.49, ALL THESE CHANGE RANDOMLY.. sometimes very good sometimes very very bad.. have to ping them to know the result b4 logging into wow nowadays.. I guess tmnet is messing up the route nowadays... zzz... |
| Change to: | 0.0135sec
0.78
5 queries
GZIP Disabled
Time is now: 4th December 2025 - 11:03 PM |