Tracert blues

[Strobemeister]

I have been having a problem logging into my World of Warcraft server, stuck at character loading screen on all toons. I did all the usual stuff, including a ip release/renew/flush rebooting everything, firewall checking etc. I've now done a tracert to the server, but I'm a bit of a noob in analyzing it. Hope someone can help, see below & sorry for upcoming wall of text. Can anyone explain the timouts? This only started happening a few days ago.

Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 11 ms 11 ms 10 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 34 ms 33 ms 34 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 34 ms 34 ms 35 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 32 ms 56 ms 31 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 32 ms 31 ms 31 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 225 ms 225 ms 225 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.89]
8 220 ms 221 ms 222 ms 4.69.162.137
9 225 ms 225 ms 225 ms ae-1-51.edge4.Amsterdam1.Level3.net [4.69.139.138]
10 218 ms 217 ms 217 ms 4.68.70.30
11 223 ms 223 ms 272 ms adm-bb4-link.telia.net [213.155.132.172]
12 274 ms 232 ms 302 ms hbg-bb2-link.telia.net [80.91.246.205]
13 235 ms 259 ms 230 ms ffm-bb2-link.telia.net [80.91.245.117]
14 236 ms 235 ms 235 ms ffm-b10-link.telia.net [80.91.251.250]
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.

 

[Strobemeister]

Ok, their website explains the 'Request timed out' notices. See below:

Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with the internet connection. To identify our servers, look for the following suffixes: telia.net,.attens.net, att.net, alter.net

Still does not solve my problem. Suggestions would be welcome.

 

[Tinuva]

Trace looks fine, only means ICMP is not affected.

 

[paddy_za]

Try with HTTP packets? I normally use PingPlotter in conjunction with WinPCap.

 

[guest2013-1]

Try with HTTP packets? I normally use PingPlotter in conjunction with WinPCap.

+1

Blizz blocks tracerts and pings