lutn-t2core-b-ge-wan63.inet.ntl.com = BROKEN

[tacook]

On the off chance that a Network Engineer from NTL might be having a look around these forums, please could you have a look at this issue, I keep getting disconnected whilst playing warcraft

Pinging lutn-t2core-b-ge-wan63.inet.ntl.com [195.182.174.197] with 32 bytes of data:

Ping statistics for 195.182.174.197:
Packets: Sent = 176, Received = 148, Lost = 28 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 683ms, Average = 67ms

[Druchii]

I'm getting the same from my UBR in a Telewest area, and i was told it's not a fault. So, if yours is a fault, then, i shall be submitting mine as well.

[dcclanuk]

Pinging 195.182.174.197 with 32 bytes of data:

Reply from 195.182.174.197: bytes=32 time=45ms TTL=248
Reply from 195.182.174.197: bytes=32 time=28ms TTL=248
Reply from 195.182.174.197: bytes=32 time=15ms TTL=248
Reply from 195.182.174.197: bytes=32 time=17ms TTL=248

Ping statistics for 195.182.174.197:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 45ms, Average = 26ms

Ping has started ...

--- 195.182.174.197 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 227.957/252.232/293.888/17.627 ms

From a Virgin.net ADSL connection (a.k.a. NTL).

[Ben]

Reply from 195.182.174.197: bytes=32 time=8ms TTL=252
Reply from 195.182.174.197: bytes=32 time=9ms TTL=252
Reply from 195.182.174.197: bytes=32 time=9ms TTL=252
Reply from 195.182.174.197: bytes=32 time=9ms TTL=252
Reply from 195.182.174.197: bytes=32 time=12ms TTL=252
Reply from 195.182.174.197: bytes=32 time=19ms TTL=252
Reply from 195.182.174.197: bytes=32 time=9ms TTL=252
Reply from 195.182.174.197: bytes=32 time=10ms TTL=252
Reply from 195.182.174.197: bytes=32 time=15ms TTL=252
Reply from 195.182.174.197: bytes=32 time=10ms TTL=252
Reply from 195.182.174.197: bytes=32 time=10ms TTL=252

It's closer to you, I'm not far from luton either

[Druchii]

100% Loss to it, seems i can't hit it with any packets...

[Chris W]

to keep this thread to a reasonable length, could we please refrain from posting line upon line of pings- the summary data from the end is much more useful. Some posted edited to make this thread a readable length.

To the OP- It is most likely that this is due to the router being under a high load (which is quite likely for a core) and it is giving low priority to ICMP traffic- hence the sporadic results.

More useful analysis of the problem can be achieved by providing traceroutes to the servers you are trying to connect to, or even better than that some pathping data (have a google for a small prog to download). We will then be able to see much more clearly what is going on.

If you were to pass the ping stats you have provided to ntl they would just throw them straight back at you as you need much more proof of a problem.

[gc7]

i tested it and got following results if they are any help

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