Tom's Hardware > Forum > General Networking > Network General Discussions > Large problem here. (tracert logs included)

Large problem here. (tracert logs included)

Forum General Networking : Network General Discussions - Large problem here. (tracert logs included)

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Ask the community Add a reply
Word :    Username :           
 
Krazedhermit   01-05-2005 at 02:58:38 AM

(I'd like to point out I'm posting about this here, as the blizzard forums are of absolutely zero help. This is my favorite tech website, so I figured it would be the best idea to post here)
Okay. So, I've been having alot of latency with a game called World of Warcraft. I've been going out of my mind as I bounce back and forth between the game company, my ISP and the makers of my DSL modem, Netopia.

The head tech or whatever was nice enough to give me a static ip address for a little while so that I could ping and run some traceroute tests to find out where the problem is. And, well, I think I figured out where the problem is. Here are the tracerts.

Take note that the 12th entry is supposed to be unreachable for whatever reason. That's what Blizzard (the maker of WoW) told me.

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 31 ms 29 ms 31 ms ***.***.***.***
2 33 ms 35 ms 31 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 35 ms 37 ms 39 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 44 ms 111 ms 167 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 75 ms 63 ms 55 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 229 ms 353 ms * sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 153 ms 127 ms 125 ms tbr2-p014001.dlstx.ip.att.net [12.123.17.86]
8 75 ms 121 ms 105 ms tbr2-cl6.sl9mo.ip.att.net [12.122.10.89]
9 94 ms 137 ms 121 ms tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
10 147 ms 127 ms 83 ms tbr1-cl2.cgcil.ip.att.net [12.122.9.133]
11 101 ms 89 ms 103 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
12 gar1-p341.nwrnj.ip.att.net [12.123.0.37] reports: Destination host unreach
able.

Trace complete.


Tracing route to 12.129.133.92 over a maximum of 30 hops

1 31 ms 29 ms 29 ms ***.***.***.***
2 32 ms 33 ms 35 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 41 ms 35 ms 33 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 52 ms 43 ms 73 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 75 ms 63 ms 69 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 127 ms 145 ms 85 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 64 ms 91 ms 47 ms tbr2-p014001.dlstx.ip.att.net [12.123.17.86]
8 79 ms 125 ms 73 ms tbr2-cl6.sl9mo.ip.att.net [12.122.10.89]
9 87 ms 89 ms 73 ms tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
10 104 ms 73 ms 129 ms tbr1-cl2.cgcil.ip.att.net [12.122.9.133]
11 87 ms 135 ms 185 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
12 * gar1-p341.nwrnj.ip.att.net [12.123.0.37] reports: Destination hos
t unreachable.


Tracing route to 12.129.133.92 over a maximum of 30 hops

1 30 ms 29 ms 29 ms ***.***.***
2 34 ms 33 ms 35 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 40 ms 33 ms 35 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 317 ms 145 ms 205 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 111 ms 95 ms 159 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 260 ms 185 ms 175 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 83 ms 123 ms 129 ms tbr2-p014001.dlstx.ip.att.net [12.123.17.86]
8 94 ms 91 ms 99 ms tbr2-cl6.sl9mo.ip.att.net [12.122.10.89]
9 85 ms 83 ms * tbr2-cl7.cgcil.ip.att.net [12.122.10.45]
10 100 ms 101 ms 137 ms tbr1-cl2.cgcil.ip.att.net [12.122.9.133]
11 247 ms 265 ms 215 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
12 gar1-p341.nwrnj.ip.att.net [12.123.0.37] reports: Destination host unreach
able.

Trace complete.

Who exactly do I contact here? Sprint? That's where it seems the issues are coming from.

<P ID="edit"><FONT SIZE=-1><EM>Edited by Krazedhermit on 01/04/05 09:01 PM.</EM></FONT></P>

Add a reply
Sponsored Links
Register or log in to remove.
folken   01-05-2005 at 08:02:32 AM
- 0 +

The destination host unreachable just means they have ICMP disabled so they don't reply to pings (a measure to prevent a denial of service attack). Your pings are up and down up and down so I'd say it is either your isp or you, more likely you. DSL routing is usually far superior to cable routing and because it is dedicated bandwidth you don't have to worry about someone hogging bandwidth and causing the spikes.
What is your current network setup at home? Have a Router? Have multiple computers? Have any apps that might be needing frequent internet access?

<A HREF="http://www.folken.net/myrig.htm" target="_new">My precious...</A>

Reply to folken
Krazedhermit   01-06-2005 at 03:01:53 AM
- 0 +

Alright. Here's what I've done in way of fixing it on my end.

I've put my modem settings to full duplex 100mbps.
I've made it so the adapter won't go to sleep to conserve power.
I've messed with checksum settings at the request of blizzard.
I've defragged my hard drive.
I always startup in selective startup without any items loading except what windows needs to run.
I've formated my hard drive and put everything back on.
I've reset my modem by pressing the little pinhole on the back and setting everything to how it needs to be.
I've put pinholes in my NAT and setup a static address for port forwarding.
And I've even bought a new ethernet card.

If there is something else to be done, I don't know what it would be exactly. I have contacted my ISP and the girl gave me a private static ip address for free for a few days so I could do some testing with it. But they otherwise say it isn't them. Though yesterday I emailed them like twenty different tracert results, all of them taken late at night when it actually gets better. I've yet to hear back so far.

Oh. And I've also moved my modem away from the monitor due to EMI fields. I don't use a router, my dsl modem goes right to the computer and the wall. And it is just me using the modem, no other computers on the network.

<P ID="edit"><FONT SIZE=-1><EM>Edited by Krazedhermit on 01/05/05 09:03 PM.</EM></FONT></P>

Reply to Krazedhermit
Krazedhermit   01-06-2005 at 06:59:56 AM
- 0 +

Here are some fresh tracert, taken just a few minutes ago. It's 12am right now. This is horrible results.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 33 ms 35 ms 37 ms 192.168.1.254
2 34 ms 35 ms 40 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 35 ms 41 ms 33 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 369 ms 507 ms 423 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 710 ms 735 ms 627 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 339 ms 345 ms * sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 453 ms 443 ms 401 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 282 ms 249 ms 183 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 139 ms 123 ms 177 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 113 ms 185 ms * tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 201 ms 167 ms 165 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination host unreac
hable.

Trace complete.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 30 ms 29 ms 29 ms 192.168.1.254
2 32 ms 33 ms 31 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 35 ms 35 ms 33 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 381 ms 367 ms 293 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 128 ms 83 ms 91 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 216 ms 283 ms 221 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 205 ms 135 ms 259 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 425 ms 477 ms 477 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 331 ms 315 ms 401 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 481 ms 439 ms 275 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 112 ms 133 ms 87 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 * gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination ho
st unreachable.

Trace complete.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 30 ms 29 ms 29 ms 192.168.1.254
2 34 ms 35 ms 39 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 35 ms 37 ms 33 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 131 ms 71 ms 81 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 65 ms 63 ms 51 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 117 ms 101 ms 120 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 49 ms * 49 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 160 ms 145 ms 199 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 216 ms 189 ms 125 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 103 ms 147 ms 161 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 128 ms 95 ms 99 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination host unreac
hable.

Trace complete.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 38 ms 32 ms 31 ms 192.168.1.254
2 34 ms 31 ms 33 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 46 ms 37 ms 31 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 90 ms 53 ms 147 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 54 ms 69 ms 55 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 60 ms 67 ms 55 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 48 ms 73 ms 57 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 102 ms 139 ms 107 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 232 ms 279 ms 201 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 97 ms 79 ms 165 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 177 ms 195 ms 193 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination host unreac
hable.

Trace complete.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 32 ms 29 ms 29 ms 192.168.1.254
2 40 ms 31 ms 33 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 45 ms 35 ms 33 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 393 ms 385 ms * sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 376 ms 299 ms 247 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 152 ms 201 ms 207 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 181 ms 163 ms 191 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 142 ms 245 ms 161 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 132 ms 99 ms 119 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 78 ms * 403 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 257 ms 173 ms 149 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination host unreac
hable.

Trace complete.

C:\Documents and Settings\KingHermit>tracert 12.129.133.92

Tracing route to 12.129.133.92 over a maximum of 30 hops

1 32 ms 39 ms 30 ms 192.168.1.254
2 40 ms 33 ms 36 ms ETCHr02.EASTEX.NET [204.96.16.252]
3 253 ms 69 ms 43 ms ETNHr02.EASTEX.NET [204.96.16.131]
4 45 ms 47 ms 45 ms sl-gw31-fw-4-1-0-TS1.sprintlink.net [160.81.63.1
29]
5 258 ms 335 ms 333 ms sl-bb21-fw-2-0.sprintlink.net [144.232.12.165]
6 367 ms 357 ms 397 ms sprint-gw.dlstx.ip.att.net [192.205.32.69]
7 341 ms 339 ms 343 ms tbr1-p012101.dlstx.ip.att.net [12.123.17.82]
8 537 ms 573 ms 485 ms tbr2-cl1.attga.ip.att.net [12.122.2.90]
9 468 ms 393 ms 355 ms tbr1-p012501.attga.ip.att.net [12.122.9.157]
10 * 380 ms 445 ms tbr2-cl1.wswdc.ip.att.net [12.122.10.69]
11 374 ms 285 ms 181 ms tbr2-cl1.n54ny.ip.att.net [12.122.10.53]
12 gar1-p3101.nwrnj.ip.att.net [12.123.0.33] reports: Destination host unreac
hable.

Trace complete.

C:\Documents and Settings\KingHermit>

Reply to Krazedhermit
sturm   01-10-2005 at 04:35:53 AM
- 0 +

there is probobly nothing you can do and nothing anyone else is going to do, or care about. Thats just the way the world is. Your pings/traceroutes times are going to depend on overall traffic on the internet, the game servers, and many other factors.
Do some pings and traceroutes on your isps equipment, if they let you, and see what the times are. If they are fine then your SOL on getting anything else done.
Know this doesnt help, just trying to be down to earth.

Reply to sturm
Ask the community Add a reply
Tom's Hardware > Forum > General Networking > Network General Discussions > Large problem here. (tracert logs included)
Go to:

There are 1081 identified and unidentified users. To see the list of identified users, Click here.

Forum map
Bestofmedia Forum ©
2000-2009 Bestofmedia Group
Page generated in 2.003 seconds
Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
Related Topics
See all relatives topics
They won a badge
Join us in greeting them
How do I win badges?