PDA

View Full Version : tracert worrying results



DeSade
31-05-2007, 09:31 AM
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Paul>tracert 206.16.13.71

Tracing route to 206.16.13.71 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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 294 ms 296 ms 296 ms 206.16.13.71

Trace complete.


This is to the Turbine LOTRO servers that I play on regularly.
After running the tracert I am worried about all the timeouts here.
What would be my next step to resolve potential issues relating to latency?

Any help would be appreciated.

stu161204
31-05-2007, 12:27 PM
Trying doing another tracert & see what you get, as I just did one to that IP address here on Xtra Go large & this is the results I get:


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

C:\Documents and Settings\Stu>tracert 206.16.13.71

Tracing route to 206.16.13.71 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 51 ms 49 ms 55 ms 210-55-67-64.adsl.netgate.net.nz [210.55.67.64]
3 55 ms * * 202.50.232.206
4 69 ms 48 ms 54 ms ge-2-3-0-42.akbr3.global-gateway.net.nz [202.50.236.113]
5 48 ms 48 ms 46 ms so1-2-0.tkbr9.global-gateway.net.nz [203.96.120.74]
6 173 ms 181 ms 176 ms so0-1-0.labr5.global-gateway.net.nz [202.50.232.26]
7 172 ms 171 ms 172 ms so2-0-0-0.labr4.global-gateway.net.nz [203.96.120.102]
8 204 ms 205 ms 204 ms sl-st20-la-6-2.sprintlink.net [144.232.154.209]
9 205 ms 203 ms 204 ms sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]
10 206 ms 204 ms 204 ms sl-crs2-ana-0-0-0-0.sprintlink.net [144.232.1.61]
11 203 ms 204 ms 203 ms sl-crs2-ana-0-8-0-0.sprintlink.net [144.232.1.72]
12 203 ms 203 ms 203 ms ggr3-p330.la2ca.ip.att.net [192.205.33.189]
13 287 ms 288 ms 288 ms 12.127.3.214
14 288 ms 298 ms 287 ms tbr2.sl9mo.ip.att.net [12.122.10.13]
15 288 ms 288 ms 288 ms tbr2.cgcil.ip.att.net [12.122.10.45]
16 287 ms 285 ms 286 ms tbr2.cb1ma.ip.att.net [12.122.10.105]
17 286 ms 285 ms 286 ms 12.127.5.89
18 288 ms 285 ms 286 ms 12-122-254-14.attens.net [12.122.254.14]
19 285 ms 285 ms 286 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.130.0.170]
20 287 ms 285 ms 286 ms 12.130.10.69
21 286 ms 285 ms 286 ms 206.16.13.71

Trace complete.

If you get the same result as you posted before, try doing another tracert to pressf1.co.nz & see what you get, if you get no results just time outs, then I would check your firewalls (maybe even disable then for a few mins & try doing a tracert again)

If that does not help, try disconnecting your modem from the internet & restart the modem & try again

Let us know how you get on.

PS: Who is your ISP?

DeSade
31-05-2007, 12:36 PM
Xtra adventure plan
Will do another trace when i get home, but this was done this morning and the ones I ran last night had the same results.

DeSade
31-05-2007, 07:02 PM
Second installment

The ping from the Turbine Server


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

C:\Documents and Settings\Paul>206.16.13.71
'206.16.13.71' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Paul>ping 206.16.13.71

Pinging 206.16.13.71 with 32 bytes of data:

Reply from 206.16.13.71: bytes=32 time=475ms TTL=233
Reply from 206.16.13.71: bytes=32 time=473ms TTL=233
Reply from 206.16.13.71: bytes=32 time=501ms TTL=233
Reply from 206.16.13.71: bytes=32 time=508ms TTL=233

Ping statistics for 206.16.13.71:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 473ms, Maximum = 508ms, Average = 489ms


Tracert from Turbine Server


C:\Documents and Settings\Paul>tracert 206.16.13.71

Tracing route to 206.16.13.71 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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 * 485 ms 481 ms 206.16.13.71

Trace complete.


Press F1 Ping


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

C:\Documents and Settings\Paul>ping pressf1.co.nz

Pinging pressf1.co.nz [210.48.100.45] with 32 bytes of data:

Reply from 210.48.100.45: bytes=32 time=72ms TTL=52
Reply from 210.48.100.45: bytes=32 time=71ms TTL=52
Reply from 210.48.100.45: bytes=32 time=69ms TTL=52
Reply from 210.48.100.45: bytes=32 time=72ms TTL=52

Ping statistics for 210.48.100.45:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 72ms, Average = 71ms

C:\Documents and Settings\Paul>


Press F1 Tracert


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

C:\Documents and Settings\Paul>tracert pressf1.co.nz

Tracing route to pressf1.co.nz [210.48.100.45]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 74 ms 79 ms 76 ms ip-210-48-100-45.iconz.net.nz [210.48.100.45]

Trace complete.

C:\Documents and Settings\Paul>


Will restart modem and try again.

DeSade
31-05-2007, 07:08 PM
Turned off firewall and retried
Same result.

Rebooted modem and tried
Same result.

As you can see by the ping to the Turbine server that latency is rather high.

DeSade
01-06-2007, 11:46 AM
Can anyone shed some light on this?

DeSade
02-06-2007, 01:26 PM
I could really use some help on this one

DeSade
05-06-2007, 09:31 AM
There must be someone that understands why this is happening......

Graham L
05-06-2007, 05:59 PM
It's just possible that all the routers on that route have been set to just drop packets (especially "non-useful" ping packets) with hopcount exceeded. Not sending them back with the error code set would cut the load on the system considerably. :cool:

DeSade
05-06-2007, 06:41 PM
Yes it is possible but how likely?