ping help

Smilie · 07-12-2003, 02:11

im having big problems with my pings
can some1 have a look at these trace routes
and tell me if these look like NTL problems???

C:\>netstat

Active Connections

Proto Local Address Foreign Address State
TCP smilie:8357 smilie.mshome.net:2869 TIME_WAIT
TCP smilie:12521 smilie.mshome.net:2869 TIME_WAIT
TCP smilie:24941 smilie.mshome.net:2869 TIME_WAIT
TCP smilie:28690 smilie.mshome.net:2869 TIME_WAIT
TCP smilie:29373 smilie.mshome.net:2869 TIME_WAIT
TCP smilie:39949 smilie.mshome.net:2869 TIME_WAIT

Trace complete.

C:\>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 * * * Request timed out.
2 38 ms 36 ms 61 ms pool-t2cam1-a-ge92.inet.ntl.com [80.5.168.1]
3 32 ms 20 ms 48 ms sot3-t2core-a-pos71.inet.ntl.com [80.4.225.9]
4 45 ms 84 ms 35 ms win-bb-a-so-020-0.inet.ntl.com [62.253.185.49]
5 24 ms 136 ms 14 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
6 69 ms 246 ms 33 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]

7 60 ms 26 ms 34 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

8 118 ms 30 ms 105 ms ams-ix.leaseweb.nl [195.69.144.215]
9 23 ms 41 ms 88 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 * * * Request timed out.
2 17 ms 25 ms 25 ms pool-t2cam1-a-ge92.inet.ntl.com [80.5.168.1]
3 66 ms 213 ms 212 ms sot3-t2core-a-pos71.inet.ntl.com [80.4.225.9]
4 59 ms 23 ms 19 ms win-bb-a-so-020-0.inet.ntl.com [62.253.185.49]
5 137 ms 24 ms 46 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
6 61 ms 12 ms 15 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]

7 31 ms 72 ms 18 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

8 25 ms 32 ms 23 ms ams-ix.leaseweb.nl [195.69.144.215]
9 42 ms 65 ms 174 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 * * * Request timed out.
2 78 ms 30 ms 51 ms pool-t2cam1-a-ge92.inet.ntl.com [80.5.168.1]
3 34 ms 11 ms 24 ms sot3-t2core-a-pos71.inet.ntl.com [80.4.225.9]
4 24 ms 78 ms 59 ms win-bb-a-so-020-0.inet.ntl.com [62.253.185.49]
5 34 ms 64 ms 39 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
6 32 ms 18 ms 21 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]

7 34 ms 24 ms 106 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

8 21 ms 20 ms 23 ms ams-ix.leaseweb.nl [195.69.144.215]
9 51 ms 32 ms 86 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 * * * Request timed out.
2 17 ms 10 ms 8 ms pool-t2cam1-a-ge92.inet.ntl.com [80.5.168.1]
3 101 ms 44 ms 27 ms sot3-t2core-a-pos71.inet.ntl.com [80.4.225.9]
4 20 ms 32 ms 97 ms win-bb-a-so-020-0.inet.ntl.com [62.253.185.49]
5 184 ms 48 ms 19 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
6 21 ms 62 ms 14 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]

7 102 ms 27 ms 51 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

8 48 ms 24 ms 71 ms ams-ix.leaseweb.nl [195.69.144.215]
9 22 ms 47 ms 23 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 * * * Request timed out.
2 22 ms 33 ms 66 ms pool-t2cam1-a-ge92.inet.ntl.com [80.5.168.1]
3 71 ms 116 ms 93 ms sot3-t2core-a-pos71.inet.ntl.com [80.4.225.9]
4 37 ms 11 ms 51 ms win-bb-a-so-020-0.inet.ntl.com [62.253.185.49]
5 11 ms 19 ms 38 ms win-bb-b-ae0-0.inet.ntl.com [213.105.172.162]
6 118 ms 11 ms 53 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]

7 24 ms 38 ms 63 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]

8 31 ms 36 ms 115 ms ams-ix.leaseweb.nl [195.69.144.215]
9 62 ms 121 ms 45 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\>ping 62.212.74.4

Pinging 62.212.74.4 with 32 bytes of data:

Reply from 62.212.74.4: bytes=32 time=22ms TTL=56
Reply from 62.212.74.4: bytes=32 time=22ms TTL=56
Reply from 62.212.74.4: bytes=32 time=65ms TTL=56
Reply from 62.212.74.4: bytes=32 time=29ms TTL=56

Ping statistics for 62.212.74.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 65ms, Average = 34ms

C:\>ping 62.212.74.4

Pinging 62.212.74.4 with 32 bytes of data:

Reply from 62.212.74.4: bytes=32 time=113ms TTL=56
Reply from 62.212.74.4: bytes=32 time=24ms TTL=56
Reply from 62.212.74.4: bytes=32 time=19ms TTL=56
Reply from 62.212.74.4: bytes=32 time=40ms TTL=56

Ping statistics for 62.212.74.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 113ms, Average = 49ms

C:\>ping 62.212.74.4

Pinging 62.212.74.4 with 32 bytes of data:

Reply from 62.212.74.4: bytes=32 time=22ms TTL=56
Reply from 62.212.74.4: bytes=32 time=31ms TTL=56
Reply from 62.212.74.4: bytes=32 time=96ms TTL=56
Reply from 62.212.74.4: bytes=32 time=24ms TTL=56

Ping statistics for 62.212.74.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 96ms, Average = 43ms

i tried looking the in-game netstats
and it seems to say i have alot of out-going packetlost
would tracert show this??

**Paul** · 07-12-2003, 02:26

I don't play games so I can't truely comment on how good they are gamewise - but those traces and pings do not have any packet loss in them and an average of about 40ms to the Netherlands doesn't seem bad to me.

Smilie · 07-12-2003, 14:04

but does tracert or ping commands show
upload packetlost???
because i suspect its my upload outgoing packet that is the problem

**Paul** · 07-12-2003, 14:54

Tracert and ping are round trip indicators - a packet is sent and a reply packet received.

carlingman · 07-12-2003, 22:08

Quote:

Originally Posted by pem

I don't play games so I can't truely comment on how good they are gamewise - but those traces and pings do not have any packet loss in them and an average of about 40ms to the Netherlands doesn't seem bad to me.

For comparison off a Non NTL connection taking tonight on 512k Pipex ADSL.

C:\DOCUME~1\ATHLON~1>tracert 62.212.74.4

Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:

1 23 ms 22 ms 21 ms XX-XX-XXX-X.dsl.pipex.com [XX.XX.XXX.X]
2 * * * Request timed out.
3 23 ms 25 ms 23 ms POS4-0.GW2.LND9.ALTER.NET [146.188.56.97]
4 22 ms 25 ms 24 ms so-4-0-0.xr1.lnd9.alter.net [158.43.150.157]
5 24 ms 23 ms 22 ms so-0-1-0.TR1.LND9.ALTER.NET [146.188.15.33]
6 28 ms 28 ms 29 ms so-5-1-0.TR1.AMS2.ALTER.NET [146.188.3.230]
7 29 ms 27 ms 28 ms POS1-0.BR1.AMS3.ALTER.NET [146.188.3.214]
8 30 ms 32 ms 28 ms 146.188.64.114
9 30 ms 31 ms 30 ms adm-bb2-pos0-3-1.telia.net [213.248.72.13]
10 32 ms 32 ms 32 ms adm-b1-pos4-0.telia.net [213.248.72.142]
11 30 ms 32 ms 30 ms leaseweb4-01768-adm-tc2-i1.c.telia.net [213.248.
72.93]
12 31 ms 34 ms 33 ms gam20.gameservers.net [62.212.74.4]

Trace complete.

C:\DOCUME~1\ATHLON~1>ping 62.212.74.4

Pinging 62.212.74.4 with 32 bytes of data:

Reply from 62.212.74.4: bytes=32 time=30ms TTL=53
Reply from 62.212.74.4: bytes=32 time=30ms TTL=53
Reply from 62.212.74.4: bytes=32 time=29ms TTL=53
Reply from 62.212.74.4: bytes=32 time=28ms TTL=53

Ping statistics for 62.212.74.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 30ms, Average = 29ms

Admin Edit:- IP Address Edited Out.

**Paul** · 07-12-2003, 22:51

Well like all things, it can depend on many factors, this is how it looks to me on my NTL connection atm;

C:\WINDOWS>ping 62.212.74.4 -t
Pinging 62.212.74.4 with 32 bytes of data:
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=40ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=27ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=25ms TTL=55
Reply from 62.212.74.4: bytes=32 time=24ms TTL=55
Reply from 62.212.74.4: bytes=32 time=26ms TTL=55
Ping statistics for 62.212.74.4:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 40ms, Average = 25ms

C:\WINDOWS>tracert 62.212.74.4
Tracing route to gam20.gameservers.net [62.212.74.4]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms W2K-PC [10.27.1.1]
2 11 ms 9 ms 10 ms 10.xxx.xxx.254
3 11 ms 8 ms 11 ms nott-t2cam1-b-ge-wan42-122.inet.ntl.com [80.4.46.201]
4 43 ms 7 ms 9 ms not-t2core-b-ge-wan64.inet.ntl.com [80.1.79.89]
5 13 ms 12 ms 11 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 23 ms 11 ms 11 ms lee-bb-a-so-600-0.inet.ntl.com [62.253.185.102]
7 26 ms 15 ms 15 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 16 ms 16 ms 15 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
9 27 ms 25 ms 36 ms amst-ic-1-so-000-0.inet.ntl.com [62.253.188.94]
10 24 ms 25 ms 24 ms ams-ix.leaseweb.nl [195.69.144.215]
11 24 ms 24 ms 25 ms gam20.gameservers.net [62.212.74.4]
Trace complete.

Smilie · 08-12-2003, 00:32

just a update

i got thru to customer support today (half an hour wait tho :

)
got to a nice helpful guy (cant remember guys name tho)

anyway he did a area utilisation test and he said it was like 95%
and it could be this that is causing me problems
he said hes passing this to the proper department to handle this
and i should get a phone call about how things r doing in this coming week

P.S

damn those ping/tracert looks much nicer then mine
i get alot of 100+ spikes
hope ill be like that in a weeks time