Kitz Forum
Computers & Hardware => Networking => Topic started by: covlad1987 on March 04, 2011, 01:30:44 PM
-
hi again is there any thing wrong with this ping and tracert test
hop 4 time out ?
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cov>tracert.www.google.co.uk
'tracert.www.google.co.uk' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\cov>tracert www.google.co.uk
Tracing route to www.l.google.com [74.125.67.103]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 29 ms 28 ms 28 ms dr3.enhmi.isp.sky.com [89.200.128.42]
3 28 ms 28 ms 28 ms vl193.ar8.enhmi.isp.sky.com [89.200.134.70]
4 * * * Request timed out.
5 29 ms 30 ms 30 ms 64.233.175.27
6 98 ms 98 ms 98 ms 209.85.250.54
7 132 ms 118 ms 117 ms 209.85.254.48
8 138 ms 119 ms 120 ms 209.85.254.249
9 131 ms 125 ms 125 ms 209.85.255.198
10 121 ms 121 ms 121 ms gw-in-f103.1e100.net [74.125.67.103]
Trace complete.
C:\Users\cov>
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\cov>tracert www.google.co.uk
Tracing route to www.l.google.com [74.125.67.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 28 ms 28 ms dr3.enhmi.isp.sky.com [89.200.128.42]
3 28 ms 28 ms 28 ms vl193.ar8.enhmi.isp.sky.com [89.200.134.70]
4 * * * Request timed out.
5 29 ms 29 ms 30 ms 64.233.175.25
6 103 ms 102 ms 102 ms 216.239.43.192
7 122 ms 121 ms 121 ms 209.85.251.9
8 122 ms 132 ms 125 ms 72.14.239.127
9 124 ms 124 ms 123 ms 209.85.255.190
10 124 ms 122 ms 122 ms gw-in-f104.1e100.net [74.125.67.104]
Trace complete.
C:\Users\cov>ping www.google.co.uk -t
Pinging www.l.google.com [74.125.67.147] with 32 bytes of data:
Reply from 74.125.67.147: bytes=32 time=121ms TTL=54
Reply from 74.125.67.147: bytes=32 time=123ms TTL=54
Reply from 74.125.67.147: bytes=32 time=123ms TTL=54
Reply from 74.125.67.147: bytes=32 time=122ms TTL=54
Reply from 74.125.67.147: bytes=32 time=122ms TTL=54
Reply from 74.125.67.147: bytes=32 time=122ms TTL=54
Reply from 74.125.67.147: bytes=32 time=121ms TTL=54
Reply from 74.125.67.147: bytes=32 time=121ms TTL=54
Reply from 74.125.67.147: bytes=32 time=120ms TTL=54
Reply from 74.125.67.147: bytes=32 time=121ms TTL=54
Reply from 74.125.67.147: bytes=32 time=120ms TTL=54
Reply from 74.125.67.147: bytes=32 time=124ms TTL=54
Reply from 74.125.67.147: bytes=32 time=125ms TTL=54
Reply from 74.125.67.147: bytes=32 time=127ms TTL=54
Reply from 74.125.67.147: bytes=32 time=126ms TTL=54
Reply from 74.125.67.147: bytes=32 time=125ms TTL=54
Reply from 74.125.67.147: bytes=32 time=124ms TTL=54
Reply from 74.125.67.147: bytes=32 time=124ms TTL=54
Ping statistics for 74.125.67.147:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 127ms, Average = 122ms
Control-C
^C
C:\Users\cov>
-
Mine's a bit faster, and hop 7 times out. (I'm on Linux so traceroute not tracert)
traceroute www.google.co.uk
traceroute: Warning: www.google.co.uk has multiple addresses; using 74.125.230.145
traceroute to www.l.google.com (74.125.230.145), 30 hops max, 46 byte packets
1 gateway.2wire.net (192.168.1.254) 24.732 ms 99.948 ms 99.984 ms
2 lns5.uan.thn.uk.murphx.net (89.145.254.75) 18.893 ms 20.046 ms 19.865 ms
3 uan-er1.uan.thn.uk.murphx.net (89.145.254.65) 18.800 ms 18.823 ms 18.740 ms
4 ge2-6-1.cr2.core.thn.uk.murphx.net (89.145.254.169) 18.665 ms 18.128 ms 18.769 ms
5 ge1-2-1.crs1.core.thn.uk.murphx.net (109.170.249.45) 18.458 ms 19.063 ms 18.722 ms
6 te2-3.cr05.tn5.bb.gxn.net (62.72.139.97) 19.244 ms 19.286 ms 18.734 ms
7 * * *
8 209.85.255.175 (209.85.255.175) 19.084 ms 209.85.252.76 (209.85.252.76) 19.394 ms 18.900 ms
9 209.85.251.58 (209.85.251.58) 19.881 ms 209.85.251.202 (209.85.251.202) 19.864 ms 19.164 ms
ping www.google.co.uk
PING www.l.google.com (74.125.230.146) 56(84) bytes of data.
64 bytes from 74.125.230.146: icmp_seq=1 ttl=56 time=19.4 ms
64 bytes from 74.125.230.146: icmp_seq=2 ttl=56 time=18.2 ms
64 bytes from 74.125.230.146: icmp_seq=3 ttl=56 time=18.2 ms
64 bytes from 74.125.230.146: icmp_seq=4 ttl=56 time=18.8 ms
64 bytes from 74.125.230.146: icmp_seq=5 ttl=56 time=18.4 ms
64 bytes from 74.125.230.146: icmp_seq=6 ttl=56 time=18.1 ms
64 bytes from 74.125.230.146: icmp_seq=7 ttl=56 time=18.7 ms
64 bytes from 74.125.230.146: icmp_seq=8 ttl=56 time=18.9 ms
64 bytes from 74.125.230.146: icmp_seq=9 ttl=56 time=18.4 ms
64 bytes from 74.125.230.146: icmp_seq=10 ttl=56 time=18.5 ms
64 bytes from 74.125.230.146: icmp_seq=11 ttl=56 time=18.5 ms
64 bytes from 74.125.230.146: icmp_seq=12 ttl=56 time=18.8 ms
64 bytes from 74.125.230.146: icmp_seq=13 ttl=56 time=17.6 ms
^C
--- www.l.google.com ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12028ms
rtt min/avg/max/mdev = 17.668/18.544/19.483/0.437 ms
Cheers,
Peter
-
Some routing sites don't respond to pings, or give them a low priority so that the returned value is high. So a timeout in one or more intermediate stages of a traceroute doesn't have any significance. For latency measurement, only the value returned by the target site matters.
-
Hi edit got beat to post :)
quote hi again is there any thing wrong with this ping and tracert test
some sites may prioritise their traffic and so time out if too busy ,some may not respond to pings at all . The main thing is to look at the Tracert results if it basically shows a gradual increase in time to its final destination then the route is probably OK.
Trace complete.
C:\Users\jeff>tracert google.co.uk
Tracing route to google.co.uk [74.125.230.113] note actually trace to uk *
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.0.1
2 38 ms 37 ms 37 ms losubs.subs.dsl1.mbr-roch.zen.net.uk [62.3.82.17
]
3 37 ms 39 ms 36 ms ae0-136.cr1.mbr-roch.zen.net.uk [62.3.80.137]
4 40 ms 39 ms 37 ms ae2-0.cr1.kp-leeds.zen.net.uk [62.3.80.70]
5 39 ms 39 ms 39 ms ge-3-1-0-0.cr2.kp-leeds.zen.net.uk [62.3.80.74]
6 45 ms 44 ms 43 ms ge-3-0-0-0.cr1.th-lon.zen.net.uk [62.3.80.78]
7 44 ms 48 ms 44 ms 72.14.217.190
8 45 ms 44 ms 43 ms 64.233.175.27
9 45 ms 45 ms 45 ms 209.85.251.62
10 43 ms 46 ms 45 ms 74.125.230.113
Trace complete.
* not www.i.google .com
I think that google has multiple addresses
Regards Jeff