I this normal with Ntl Broadband?

JM MARCONI

Should i have that much packet loss. i think this is why i have a red ping in Rainbow 6 vegas

Cal

That is not packet loss. That is outgoing packets sent from your network card and incomming packets recieved.

Cal.

JM MARCONI

Ok so what does that mean? And also how do i check for packet loss?

Thanks

tman

stick your hand down your pants...




or you could go to start > run > cmd > "ping boards.ie -n 50"

JM MARCONI

Ok i did that. it doesnt give me a result though. The screen just closes.
Any suggestions? Putting my hand down my pants helped a bit

JM MARCONI

Sorry, my bad! The results are
Packets sent 50 Recieved 49 Lost 1 (2% Loss)

Approx Round Trip Times in milli seconds
Min 47ms Max 67ms Average 49ms.

Is this good? Also would this be the reason for Red dot pings in games?

daymobrew

JM MARCONI wrote:

Ok so what does that mean? And also how do i check for packet loss?

When you request a page from the internet it might only take a small amount of data, but the returned data is going to be much higher, therefore more packets incoming than outgoing.

Did you enter 'cmd' in the Start/Run dialog? That will bring up a command prompt. Then type ping boards.ie -n 50. After it sends 50 packages to boards.ie it will display results. Here is what I see for 4 packets:

~> ping boards.ie -n 4

Pinging boards.ie [82.195.136.250] with 32 bytes of data:

Reply from 82.195.136.250: bytes=32 time=51ms TTL=52
Reply from 82.195.136.250: bytes=32 time=51ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=51ms TTL=52

Ping statistics for 82.195.136.250:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 51ms, Average = 50ms

The data values will be different for you, and different each time you run the command. The Lost value will be of interest. It should be 0 or very close to 0.

JM MARCONI

ping boards.ie -n 4

Pinging boards.ie [82.195.136.250] with 32 bytes of data:

Reply from 82.195.136.250: bytes=32 time=84ms TTL=49
Reply from 82.195.136.250: bytes=32 time=112ms TTL=49
Reply from 82.195.136.250: bytes=32 time=91ms TTL=49
Reply from 82.195.136.250: bytes=32 time=79ms TTL=49

Ping statistics for 82.195.136.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 112ms, Average = 91ms

Thats When i send 4

tman

4 won't tell you anything (unless it's a seriously bad connection)
you're better off trying a higher number, like 50

JM MARCONI

ping boards.ie -n 50
Pinging boards.ie [82.195.136.250] with 32 bytes of data:

Reply from 82.195.136.250: bytes=32 time=78ms TTL=52
Reply from 82.195.136.250: bytes=32 time=68ms TTL=52
Reply from 82.195.136.250: bytes=32 time=82ms TTL=52
Reply from 82.195.136.250: bytes=32 time=55ms TTL=52
Reply from 82.195.136.250: bytes=32 time=51ms TTL=52
Reply from 82.195.136.250: bytes=32 time=58ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=57ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=52ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=65ms TTL=52
Reply from 82.195.136.250: bytes=32 time=52ms TTL=52
Reply from 82.195.136.250: bytes=32 time=59ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=67ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=66ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=57ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=60ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=51ms TTL=52
Reply from 82.195.136.250: bytes=32 time=47ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=49ms TTL=52
Reply from 82.195.136.250: bytes=32 time=48ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52
Reply from 82.195.136.250: bytes=32 time=50ms TTL=52

Ping statistics for 82.195.136.250:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 82ms, Average = 52ms

Its annoying because the only 3 people in my clan who can host matches i have a Red ping in there rooms. And they are only in England

steveland?

That means you sent 50 packets and all were received. There was no packet loss there (a good thing).

Stark

I'm getting 8% packet loss with them tonight. The other night it was 25%. ****ing **** service.

Stark

Had between 22% and 28% packet loss for most of today. It's only usable again now. Time to get DSL installed I reckon.

HairyMammoth

I presume you are playing an online game, if so, try tracing to the server you are playing from. See where the server is located. See if there is network conjestion. It may not be NTL network causing ping latency.

bobzee

I have been an NTL broadband customer for about 7 Months...initially the service was great..I am on a 2mb line and was getting close to 1.7mb download speeds.. For the last 3 months however I have been getting really poor speeds <1mb, sometimes even as low as 100k...and lots of packet loss...up to 45% on some occasions.

i mainly use my broadband to connect to the office via a vpn so obviously the packet loss causes major problems. I have reported the issues to NTL many many times...and just before Christmas i got a call from their second line support team who explained that the problem is that becuase there are lots of subscribers on each node..some users are vastly exceeded their upload and download quota's ie. they are torrenting all the time....and ntl have no way of identifying which subscribers are causing the problem....and so cannot terminate their connections. Apparently they only see the usage on a node..not an individual subscriber. According to the support guy, these subscribers are causing the connection issues for other users on that node. he told me it should be resolved in the new year...which it aint

I sent another complaint to them last week which I haven't even got a response to yet....In my view..NTL do not have the ability to offer an 'always-on' service if they cannot identify and deal with users who are effecting other subscribers connections by using too much bandwidth....

these days I actually resort to using plain old dial up to check my mail..as the broadband is just too un-reliable...its an appaling service..from an appaling company.

Stark

HairyMammoth wrote:

I presume you are playing an online game, if so, try tracing to the server you are playing from. See where the server is located. See if there is network conjestion. It may not be NTL network causing ping latency.

Not so.

Neither myself nor my housemates have been able to use NTL to browse the web during the times of high packet loss. We got everyone to disconnect from the net to test it out, and ran the ping command to traditionally reliable sites such as google.ie from one laptop hooked directly to the cable modem. During the times where the web was unusable, the packet loss ranged from 25% to 60%. Always in the evening times between about 6pm and 11pm. 8% would have been a "good" evening.

It seemed to be okay last night when I came home, let's hope it stays that way. NTL customer support has been totally useless in helping us with the matter.