TechSpot

Internet/LAN Lagging Everyone 20 Seconds

By Zolga
Nov 17, 2007
  1. hello everyone

    Ive bought a new router because of this fault and i have no idea whats wrong. It happens again =[

    I have pinged my Router IP and another IP from the internet "85.234.155.52" which is teamhost.

    I get this high ping like every 20 seconds

    I get this,
    From my LAN ip
    Code:
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=875ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    From internet ip,
    Code:
    Reply from 85.234.155.52: bytes=32 time=73ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=63ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=75ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=66ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=73ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=66ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=72ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=84ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=68ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=958ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=41ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=77ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=66ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=70ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=76ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=61ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=66ms TTL=57
    It happens at the same time :S
    Can any suggest what's wrong?
    Could this be my ISP or something? =[
    thanks
     
  2. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    And sometimes this happens, for 5 minutes or longer.

    Code:
    Reply from 85.234.155.52: bytes=32 time=639ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=505ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=625ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=581ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=322ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=734ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=488ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=495ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=516ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=335ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=547ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=450ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=578ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=555ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=604ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=564ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=503ms TTL=57
    Reply from 85.234.155.52: bytes=32 time=371ms TTL=57
    Code:
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
    Here is also a tracert of when this happens.

    Code:
    Tracing route to teamhost.co.uk [85.234.155.52]
    over a maximum of 30 hops:
    
      1     1 ms     2 ms     1 ms  192.168.1.1
      2   413 ms   476 ms   464 ms  10.251.68.1
      3   499 ms   511 ms   539 ms  leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217]
      4   561 ms   365 ms   327 ms  cpc3-ches1-3-1-cust237.lutn.cable.ntl.com [82.3.
    32.237]
      5   536 ms   439 ms   353 ms  nth-bb-b-so-130-0.inet.ntl.com [213.105.172.41]
    
      6   571 ms   532 ms   447 ms  tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
      7   622 ms   634 ms   560 ms  212.250.14.90
      8   323 ms   323 ms   676 ms  ge-5-2.the.uk.euroconnex.net [87.127.231.90]
      9   527 ms   307 ms   452 ms  webhosting.teamhost.co.uk [85.234.155.52]
    
    Trace complete.
     
  3. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    anyone know =[?
    I cannot play ANY games or do anything almost.
    except browse the internet
     
  4. jobeard

    jobeard TS Ambassador Posts: 9,330   +622

    try pathping 85.234.155.52

    let it run to completion and it will report where the packets are being lost.
     
  5. mikescorpio81

    mikescorpio81 TS Rookie Posts: 293

    That really shouldn't affect your gaming. It's not like you are losing packets, only 1 packet is high and it reaches the destination.

    Try updating the DNS servers in your router with the latest (obtain from your ISP).
     
  6. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    I did that ping thing. and it does effect my gaming, i lag for that one second. =[
    Router obtains DNS auto.

    Code:
    Tracing route to webhosting.teamhost.co.uk [85.234.155.52]
    over a maximum of 30 hops:
      0  daniel-86c63676 [192.168.1.2]
      1  192.168.1.1
      2  10.251.68.1
      3  leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217]
      4  cpc3-ches1-3-1-cust237.lutn.cable.ntl.com [82.3.32.237]
      5  nth-bb-b-so-130-0.inet.ntl.com [213.105.172.41]
      6  tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
      7  212.250.14.90
      8  ge-5-2.the.uk.euroconnex.net [87.127.231.90]
      9  webhosting.teamhost.co.uk [85.234.155.52]
    
    Computing statistics for 225 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           daniel-86c63676 [192.168.1.2]
                                    0/ 100 =  0%   |
      1   42ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                   14/ 100 = 14%   |
      2  ---     100/ 100 =100%    86/ 100 = 86%  10.251.68.1
                                    0/ 100 =  0%   |
      3  248ms    18/ 100 = 18%     4/ 100 =  4%  leic-t2cam1-b-v104.inet.ntl.com [8
    2.3.35.217]
                                    0/ 100 =  0%   |
      4  242ms    15/ 100 = 15%     1/ 100 =  1%  cpc3-ches1-3-1-cust237.lutn.cable.
    ntl.com [82.3.32.237]
                                    0/ 100 =  0%   |
      5  223ms    20/ 100 = 20%     6/ 100 =  6%  nth-bb-b-so-130-0.inet.ntl.com [21
    3.105.172.41]
                                    0/ 100 =  0%   |
      6  233ms    14/ 100 = 14%     0/ 100 =  0%  tele-ic-1-as0-0.inet.ntl.com [62.2
    53.184.2]
                                    0/ 100 =  0%   |
      7  ---     100/ 100 =100%    86/ 100 = 86%  212.250.14.90
                                    0/ 100 =  0%   |
      8  230ms    14/ 100 = 14%     0/ 100 =  0%  ge-5-2.the.uk.euroconnex.net [87.1
    27.231.90]
                                    1/ 100 =  1%   |
      9  224ms    15/ 100 = 15%     0/ 100 =  0%  webhosting.teamhost.co.uk [85.234.
    155.52]
    
    Trace complete.
     
  7. jobeard

    jobeard TS Ambassador Posts: 9,330   +622

    Code:
      1   42ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                   [COLOR="Red"]14/ 100 = 14% [/COLOR]  |
      2  ---     100/ 100 =100%    [COLOR="Red"]86/ 100 = 86%[/COLOR]  10.251.68.1
                                    0/ 100 =  0%   |
      3  248ms    18/ 100 = 18%     4/ 100 =  4%  leic-t2cam1-b-v104.inet.ntl.com [8
    2.3.35.217]
                                    0/ 100 =  0%   |
      4  242ms    15/ 100 = 15%     1/ 100 =  1%  cpc3-ches1-3-1-cust237.lutn.cable.
    ntl.com [82.3.32.237]
                                    0/ 100 =  0%   |
      5  223ms    20/ 100 = 20%     6/ 100 =  6%  nth-bb-b-so-130-0.inet.ntl.com [21
    3.105.172.41]
                                    0/ 100 =  0%   |
      6  233ms    14/ 100 = 14%     0/ 100 =  0%  tele-ic-1-as0-0.inet.ntl.com [62.2
    53.184.2]
                                    0/ 100 =  0%   |
      7  ---     100/ 100 =100%    [COLOR="Red"]86/ 100 = 86% [/COLOR] 212.250.14.90
                                    0/ 100 =  0%   |
      8  230ms    14/ 100 = 14%     0/ 100 =  0%  ge-5-2.the.uk.euroconnex.net [87.1
    27.231.90]
                                    1/ 100 =  1%   |
      9  224ms    15/ 100 = 15%     0/ 100 =  0%  webhosting.teamhost.co.uk [85.234.
    155.52]
    
    OUCH!
    Your 192.168.1.1 and 10.251.68.1 devices are a major problem!
    14 and 86% losses are unacceptable; normal rates are 0-2%
    Notice the 14% is on the line between the two devices!
    The loss rates displayed for the links, identified as a vertical bar (|) in the Address column, indicate link congestion that is causing the loss of packets that are being forwarded on the path. The loss rates displayed for routers (identified by their IP addresses) indicate that these routers might be overloaded.​
    see this for details
    212.250.14.90 has 86% loss to, but you can't fix that.
     
  8. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    so how can i fix?
     
  9. jobeard

    jobeard TS Ambassador Posts: 9,330   +622

    let's go through the devices one at a time:
    tell us about each of these:
    0 daniel-86c63676 [192.168.1.2] << this is your system
    1 192.168.1.1 << connected to this: what is it
    2 10.251.68.1 << most important, what is this?
    3 499 ms 511 ms 539 ms leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217] << should be your ISP Gateway

    >a new router
    which device, 1 or 2 ? and why did you chose multiple routers?
     
  10. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    192.168.1.1 is my router.
    10.251.68.1 i dont know.

    i bought new router because i thought it was the router....

    this is what i get when i ping 10.251.68.1
    Code:
    Pinging 10.251.68.1 with 32 bytes of data:
    
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    
    Ping statistics for 10.251.68.1:
        Packets: Sent = 6, Received = 0, Lost = 6 (100% loss)
    i also did pathping again
    Code:
    Tracing route to teamhost.co.uk [85.234.155.52]
    over a maximum of 30 hops:
      0  daniel-86c63676 [192.168.1.2]
      1  192.168.1.1
      2  10.251.68.1
      3  leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217]
      4  cpc3-ches1-3-1-cust237.lutn.cable.ntl.com [82.3.32.237]
      5  nth-bb-b-so-130-0.inet.ntl.com [213.105.172.41]
      6  tele-ic-1-as0-0.inet.ntl.com [62.253.184.2]
      7  212.250.14.90
      8  ge-5-2.the.uk.euroconnex.net [87.127.231.90]
      9  webhosting.teamhost.co.uk [85.234.155.52]
    
    Computing statistics for 225 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           daniel-86c63676 [192.168.1.2]
                                    0/ 100 =  0%   |
      1   43ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                    0/ 100 =  0%   |
      2  ---     100/ 100 =100%   100/ 100 =100%  10.251.68.1
                                    0/ 100 =  0%   |
      3   36ms     0/ 100 =  0%     0/ 100 =  0%  leic-t2cam1-b-v104.inet.ntl.com [8
    2.3.35.217]
                                    0/ 100 =  0%   |
      4   26ms     0/ 100 =  0%     0/ 100 =  0%  cpc3-ches1-3-1-cust237.lutn.cable.
    ntl.com [82.3.32.237]
                                    0/ 100 =  0%   |
      5   16ms     0/ 100 =  0%     0/ 100 =  0%  nth-bb-b-so-130-0.inet.ntl.com [21
    3.105.172.41]
                                    0/ 100 =  0%   |
      6   17ms     0/ 100 =  0%     0/ 100 =  0%  tele-ic-1-as0-0.inet.ntl.com [62.2
    53.184.2]
                                    0/ 100 =  0%   |
      7  ---     100/ 100 =100%   100/ 100 =100%  212.250.14.90
                                    0/ 100 =  0%   |
      8   25ms     0/ 100 =  0%     0/ 100 =  0%  ge-5-2.the.uk.euroconnex.net [87.1
    27.231.90]
                                    0/ 100 =  0%   |
      9   17ms     0/ 100 =  0%     0/ 100 =  0%  webhosting.teamhost.co.uk [85.234.
    155.52]
    
    Trace complete.
     
  11. jobeard

    jobeard TS Ambassador Posts: 9,330   +622

    Code:
      [COLOR="Red"]2[/COLOR]  ---     100/ 100 =100%   100/ 100 =100%  10.251.68.1
      [COLOR="Red"]3 [/COLOR]  36ms     0/ 100 =  0%     0/ 100 =  0%  leic-t2cam1-b-v104.inet.ntl.com [82.3.35.217]
     [COLOR="Red"] 7 [/COLOR] ---     100/ 100 =100%   100/ 100 =100%  212.250.14.90
    
    [3] is your ISP gateway, but apparently [2] & [7] are configured to NOT respond
    to PING. if they actually lost all 100% of the traffic, you would never get to teamhost.co.uk at all

    [2] is apparently another router between you and the gateway for ntl.com [3]

    All I can recommed is calling the ISP helpdesk and showing them the pathping
    results; complain about the bad response times you're getting.
     
  12. mikescorpio81

    mikescorpio81 TS Rookie Posts: 293

    I would change the DNS servers within your router to known DNS servers in your area/state/country/whatever. The first hop from LAN to WAN seems to be causing the problem. By changing the DNS servers within your router it should get around it.

    But I would too flag it with your ISP.
     
  13. jobeard

    jobeard TS Ambassador Posts: 9,330   +622

    changing the DNS seldom works as the new one will not like being accessed outside its own domain; at least that is my experience.

    I've see the intermediate router like 10.251.68.1 several times now but usually
    with satalite access, not cable or dsl (via telco).
     
  14. mikescorpio81

    mikescorpio81 TS Rookie Posts: 293

    There are quite a few public DNS servers out in the world that you can use as your own DNS server, even if they aren't your ISP.
    It is best practice to use DNS servers provided by your ISP (speed), but as I said there are alot out there that will do DNS lookups for anyone.
    Google DNS servers in your state and ping each one for around 30-40 packets. The fastest response time would be a good one to use (as a test).

    If you do find a good one, give yourself a static IP address in the same range as your LAN and use the new DNS server as your preferred DNS server. If you then notice that your pings have improved, update your router's DNS servers.
     
  15. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    i just tried DNS changing but it does the same =/ high ping every 20 seconds.
    Sometimes when my friend and i are playing CSS together we get a constant high ping like 800 m/s
     
  16. mikescorpio81

    mikescorpio81 TS Rookie Posts: 293

    Try booting into Safe Mode with Networking and run through your ping tests again. This will rule out whether a program is causing the crazy ping.

    What are your routers current DNS servers?

    When you changed your DNS server, did you assign yourself a static IP address and put in a new preferred DNS server? If so, what is the IP address of the new DNS server?

    Have you updated your NIC's drivers?
    Have you factory reset your router and/or firmware upgraded your router?
    Have you tried a different patch cable?

    If all of this fails, it is either your NIC or a line problem (ISP).
     
  17. Zolga

    Zolga TS Rookie Topic Starter Posts: 56

    ok ill try that

    the dns server i tried were opendns ones. now ive set it auto.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...