A little advice

[Maverich]

Good evening all 

Just wondering if someone can clarify the problem I seem to be having with my connection.  The main concern is online gaming when all of a sudden it becomes very 'jittery'. After doing some research I see someone mention packet loss.  Does anyone know how I can check this or fix this?

Thanks in advance 

ADSL Link   Downstream   Upstream
Connection Speed   8128 kbps   448 kbps
Line Attenuation   31.0 db   18.0 db
Noise Margin   5.4 db   17.0 db

Not sure if you need this 

[Rik]

We don't. Ping www.idnet.net and one of your games servers. If you're not sure how to run a ping, just ask.

[Maverich]

This is what I received from idnet.net.  I'm unsure as to which server the game runs on    I also done a ping to bbc.co.uk earlier and i dropped 1 packet 

Reply from 212.69.36.10: bytes=32 time=27ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59

[Glenn]

If you use ping 212.69.36.10 -n 100 it will ping 100 times, it should give a getter indication of packet loss rather then just 4 pings

[Maverich]

Thanks, does make more sense 

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=79ms TTL=59
Reply from 212.69.36.10: bytes=32 time=84ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=96ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=105ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=26ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=29ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Request timed out.
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=25ms TTL=59
Reply from 212.69.36.10: bytes=32 time=22ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=18ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
    Minimum = 18ms, Maximum = 105ms, Average = 24ms

[Glenn]

Reply from 212.69.36.10: bytes=32 time=79ms TTL=59
Reply from 212.69.36.10: bytes=32 time=84ms TTL=59
Reply from 212.69.36.10: bytes=32 time=89ms TTL=59
Reply from 212.69.36.10: bytes=32 time=96ms TTL=59
Reply from 212.69.36.10: bytes=32 time=99ms TTL=59
Reply from 212.69.36.10: bytes=32 time=105ms TTL=59

That will push up your latency in game, there is also 1 packet lost. All this maybe that the server you have 'pinged' is busy, as a ping packet has very low priority.

[Maverich]

That sounds fair enough, maybe not a problem with packet loss...I am also finding that loading small pictures on the internet taking time like i'm on a dial up connection, then all of a sudden it speeds up again and no problem at all.  This ties into what is happening on xbox live, one min the game is running fine then for about 20-30 secs it really struggles.  Any ideas?

[Rik]

It could be a 'hot VP' (exchange congestion) or VLAN issue (the way your circuit has been built.

Do some speed tests on the BT tester, say morning, lunchtime and evening, plus a few sets of -n 100 pings, and then let support have the data, they can take it from there.

[Maverich]

Thanks Rik 

[Rik]

NP. Hope it's sorted soon.