Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

NTL D16 service hosed

Options
  • 26-05-2007 10:35pm
    #1
    Registered Users Posts: 27,163 ✭✭✭✭


    ok, I am getting very sick of being unable to play any sort of online games lately or connect to a VPN for more than 10 minutes at a time.
    After getting booted for the 5th time in 15 minutes I just ran a few stats:
    C:\>tracert www.yahoo.co.uk
    
    Tracing route to www.euro.yahoo-eu1.akadns.net [217.146.186.51]
    over a maximum of 30 hops:
    
      1    <1 ms    31 ms     6 ms  192.168.0.1
      2    45 ms   700 ms  2996 ms  10.91.0.1
      3   263 ms   240 ms   259 ms  089-101-162001.ntlworld.ie [89.101.162.1]
      4   129 ms   170 ms   255 ms  213.46.165.49
      5    52 ms    93 ms    75 ms  nl-ams-rc-02-pos-2-0.chellonetwork.com [213.46.160.17]
      6   726 ms  3375 ms    50 ms  213.46.174.78
      7    52 ms  1850 ms  2683 ms  ldn-b1-pos1-3.telia.net [213.248.78.129]
      8   125 ms    61 ms    23 ms  ldn-bb1-pos0-3-0.telia.net [213.248.74.5]
      9   919 ms  3437 ms   158 ms  dln-b1-link.telia.net [80.91.250.85]
     10    79 ms  4072 ms    87 ms  yahoo-115023-dln-b1.c.telia.net [213.155.141.182]
     11    68 ms  2283 ms  1710 ms  gi-1-3.bas-a1.ird.yahoo.com [217.146.191.137]
     12    83 ms    38 ms    43 ms  www.vip.ird.yahoo.com [217.146.186.51]
    
    Trace complete.
    
    C:\>ping -t www.yahoo.com
    
    Pinging www.yahoo-ht3.akadns.net [69.147.114.210] with 32 bytes of data:
    
    Reply from 69.147.114.210: bytes=32 time=377ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=378ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=174ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=339ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=177ms TTL=53
    Request timed out.
    Reply from 69.147.114.210: bytes=32 time=135ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=170ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=866ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=2819ms TTL=53
    Reply from 69.147.114.210: bytes=32 time=177ms TTL=53
    
    Ping statistics for 69.147.114.210:
        Packets: Sent = 11, Received = 10, Lost = 1 (9% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 135ms, Maximum = 2819ms, Average = 561ms
    
    
    Is this a joke?


Comments

  • Registered Users Posts: 27,163 ✭✭✭✭GreeBo


    ok if I remove my router (wireless but Im wired to it) the pings get much better..any ideas?
    No one else is using the connection but for some reason its killing my pings...
    This was fine up until recently...? :(


  • Closed Accounts Posts: 2,279 ✭✭✭DemonOfTheFall


    What router is it?

    I got a netgear from NTL and that used to add up to 10ms to my pings, but nothing like what you're experiencing.


  • Registered Users Posts: 27,163 ✭✭✭✭GreeBo


    Its a D-Link Ive had for a while but its always been rock solid.


  • Registered Users Posts: 856 ✭✭✭andrew163


    Wouldn't be overheating by any chance would it?


  • Registered Users Posts: 335 ✭✭donal.hunt


    1 <1 ms 31 ms 6 ms 192.168.0.1
    2 45 ms 700 ms 2996 ms 10.91.0.1

    so the latency is between your dlink router and NTL's UBR. as you've pointed out removing the router improves the latency. in the future, winmtr will combine traceroute style output with ping and let you monitor the link after a period of time (useful for analysing where issues are occuring).

    if it is the dlink router try a firmware upgrade / tweaking the settings.

    re: the topic. always check how widespread an issue is before assuming it's a geographical problem. 1/2 of the NTL related issues on this forum are people bitching without the facts to back up their statements and/or reporting the issue to NTL directly.


  • Advertisement
  • Registered Users Posts: 27,163 ✭✭✭✭GreeBo


    I think it might be overheating allright, Im moving to a more ventilated space (and aadding a few spare case fans :) )

    re the topic, my NTL is still crap as the connection drops frequently whether Im hardwired or not, making working from home over VPN impossible some days.
    but I take your point.


Advertisement