Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: is this normal  (Read 6185 times)

covlad1987

  • Reg Member
  • ***
  • Posts: 171
is this normal
« on: October 12, 2011, 11:21:13 AM »

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\joe>tracert www.google.co.uk

Tracing route to www.l.google.com [209.85.147.106]
over a maximum of 30 hops:

  1    90 ms    98 ms    99 ms  O2wirelessbox.lan [192.168.1.254]
  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    34 ms     *       29 ms  bru01m01-in-f106.1e100.net [209.85.147.106]

Trace complete.

C:\Users\joe>
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: is this normal
« Reply #1 on: October 12, 2011, 11:47:18 AM »

Timeouts on intermediate servers in a route trace are usually just the result of those servers giving a low priority to ping responses. You might get a different result at different times. I'm not familiar with Windows' version of traceroute, but I expect there are extra parameters which you can specify to change the timeout, or to specify a different type of ping protocol.
Logged
  Eric

covlad1987

  • Reg Member
  • ***
  • Posts: 171
Re: is this normal
« Reply #2 on: October 12, 2011, 11:55:07 AM »

Timeouts on intermediate servers in a route trace are usually just the result of those servers giving a low priority to ping responses. You might get a different result at different times. I'm not familiar with Windows' version of traceroute, but I expect there are extra parameters which you can specify to change the timeout, or to specify a different type of ping protocol.

the last 4 times i tracert have all been the same ping test are showing nothing not lost any
Logged

jeffbb

  • Kitizen
  • ****
  • Posts: 2329
Re: is this normal
« Reply #3 on: October 12, 2011, 06:21:05 PM »

Hi
I am surprised you do not see your own ISP in the tracert .
It is unusual to see so many timed out on the route  .
Have you tried others like bbc.co.uk
Regards Jeff
Logged
zen user

covlad1987

  • Reg Member
  • ***
  • Posts: 171
Re: is this normal
« Reply #4 on: October 13, 2011, 12:30:55 AM »

Hi
I am surprised you do not see your own ISP in the tracert .
It is unusual to see so many timed out on the route  .
Have you tried others like bbc.co.uk
Regards Jeff

latest one iv moved all cables away from any thing that could be a problem also using the test socket
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\joe>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

  1    59 ms    99 ms    98 ms  O2wirelessbox.lan [192.168.1.254]
  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    20 ms    19 ms    20 ms  bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

C:\Users\joe>


  1    59 ms    99 ms    98 ms  O2wirelessbox.lan [192.168.1.254]
  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    20 ms    19 ms    20 ms  bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.

C:\Users\joe>

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\joe>ping www.bbc.co.uk -t

Pinging www.bbc.net.uk [212.58.244.70] with 32 bytes of data:
Reply from 212.58.244.70: bytes=32 time=24ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=23ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=22ms TTL=55
Reply from 212.58.244.70: bytes=32 time=20ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=28ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=22ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=20ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55
Reply from 212.58.244.70: bytes=32 time=21ms TTL=55

Ping statistics for 212.58.244.70:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 20ms, Maximum = 28ms, Average = 21ms
Control-C
^C
C:\Users\joe>
« Last Edit: October 13, 2011, 12:35:28 AM by covlad1987 »
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: is this normal
« Reply #5 on: October 13, 2011, 07:31:24 AM »

There is a definite oddity about these results. As Jeff said, you would normally expect to get results from your own ISP's servers, even if the other servers along the route were timing out. I wonder if this is something to do with your DNS setup - what DNS servers do you use?

Of course, in a sense this is all academic, because the only line in a tracert which really matters from a functional point of view is the last one. If you're getting low ping values from the target site, then your connection to that site is good.
Logged
  Eric

Oranged

  • Reg Member
  • ***
  • Posts: 623
    • The Mobile Help Forum
Re: is this normal
« Reply #6 on: October 13, 2011, 11:20:34 AM »

BE/O2 are currently experiencing problems on LINX GW2 which has been reported on BE Usergroup and O2 forum and has been shown on their status pages. Here's mine which is using LINX GW1

Quote
C:\Documents and Settings\N>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

  1    47 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    38 ms    23 ms    23 ms  bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
  6    39 ms    22 ms    24 ms  212.58.238.133
  7    39 ms    24 ms    24 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  8    39 ms    24 ms    25 ms  212.58.255.12
  9    38 ms    23 ms    22 ms  bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.
Logged

covlad1987

  • Reg Member
  • ***
  • Posts: 171
Re: is this normal
« Reply #7 on: October 13, 2011, 12:00:50 PM »

BE/O2 are currently experiencing problems on LINX GW2 which has been reported on BE Usergroup and O2 forum and has been shown on their status pages. Here's mine which is using LINX GW1

Quote
C:\Documents and Settings\N>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.94]
over a maximum of 30 hops:

  1    47 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5    38 ms    23 ms    23 ms  bbc-gw1-linx.prt0.thdoe.bbc.co.uk [195.66.226.10
3]
  6    39 ms    22 ms    24 ms  212.58.238.133
  7    39 ms    24 ms    24 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
  8    39 ms    24 ms    25 ms  212.58.255.12
  9    38 ms    23 ms    22 ms  bbc-vip015.cwwtf.bbc.co.uk [212.58.246.94]

Trace complete.

cheers so its there end least then i dont have to call them up lol what is LINX GW2 ??????

Logged

Oranged

  • Reg Member
  • ***
  • Posts: 623
    • The Mobile Help Forum
Re: is this normal
« Reply #8 on: October 13, 2011, 12:07:20 PM »

Logged

covlad1987

  • Reg Member
  • ***
  • Posts: 171
Re: is this normal
« Reply #9 on: October 13, 2011, 12:19:24 PM »

Logged

covlad1987

  • Reg Member
  • ***
  • Posts: 171
Re: is this normal
« Reply #10 on: October 15, 2011, 01:10:31 PM »

what i dont get is on the tracert the fisrt hop comes up 1    47 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]

but if i just tracert the ip it comes up with 1ms 1ms 1ms like you all have said not to worry


ANY IDEA what part of the forum i can put this info

Error Seconds (Local/Remote):   354 / 0
FEC Errors (Up/Down):   152,917,770 / 152,917,770
CRC Errors (Up/Down):   596 / 291
HEC Errors (Up/Down):   432 / 108
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: is this normal
« Reply #11 on: October 15, 2011, 03:38:14 PM »

Quote
what i dont get is on the tracert the fisrt hop comes up 1    47 ms    99 ms    99 ms  O2WirelessBox.lan [192.168.1.254]

That's not uncommon, and it probably reflects the fact that the the router also gives a low priority to ping requests.

If you've got a question about errors, please raise it in Broadband - ADSL issues.
Logged
  Eric
 

anything