graph help

Hi,

Could someone give me your thought on what the graph below means for packet loss:

graph

The line is on a rural exchange and the bt checker says the line can only get up to 0.5 meg to 3 meg.

The router was a vigor 2820n and was syncing at 6 meg. The end user was reporting blocky/slow RDP sessions and when this was happening I noticed the packet loss.

I replaced the router/filterwith a Netgear 834GT with DGTeam firmware and forced the SNR to effectively sync at 3 meg (which is what the above graph represents)

Here's the dmt tool output:

dmt output

The end user has another ADSL line with a different provider and when they try RDP on that, they get no slow downs and blockyness.

ISP says on their test, there is no problem with the line, even if the TBB graph snows packet loss.

I've not pugged the router in the test socket but wonder if anyone has any thoughts on what I can try next?

Thank You

To make sure it isn't just TBB I would recommend setting another graph over at f8lure.

http://f8lure.mouselike.org/auth.asp

You could also set the graphs up for your Exchange to see if packetloss is recorded there as well.

I forgot to say I'd done that... f8luresig so, looks the same....

Also command line pings running ever 10 mins... show this...

nic_2013-05-17-11-43-37 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-11-57-14 Sent = 200, Received = 193, Lost = 7 (3% loss),
nic_2013-05-17-12-11-05 Sent = 200, Received = 187, Lost = 13 (6% loss),
nic_2013-05-17-12-25-23 Sent = 200, Received = 193, Lost = 7 (3% loss),
nic_2013-05-17-12-39-14 Sent = 200, Received = 193, Lost = 7 (3% loss),
nic_2013-05-17-12-53-04 Sent = 200, Received = 199, Lost = 1 (0% loss),
nic_2013-05-17-13-06-28 Sent = 200, Received = 199, Lost = 1 (0% loss),
nic_2013-05-17-13-19-51 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-13-33-28 Sent = 200, Received = 194, Lost = 6 (3% loss),
nic_2013-05-17-14-00-39 Sent = 200, Received = 197, Lost = 3 (1% loss),
nic_2013-05-17-14-27-31 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-15-07-55 Sent = 200, Received = 192, Lost = 8 (4% loss),
nic_2013-05-17-16-01-57 Sent = 200, Received = 195, Lost = 5 (2% loss),
nic_2013-05-17-16-15-38 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-16-29-15 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-16-42-43 Sent = 200, Received = 192, Lost = 8 (4% loss),
nic_2013-05-17-16-56-38 Sent = 200, Received = 188, Lost = 12 (6% loss),
nic_2013-05-17-17-10-51 Sent = 200, Received = 194, Lost = 6 (3% loss),
nic_2013-05-17-17-24-37 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-17-38-05 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-17-51-42 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-18-05-10 Sent = 200, Received = 192, Lost = 8 (4% loss),
nic_2013-05-17-18-32-24 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-20-45-48 Sent = 200, Received = 193, Lost = 7 (3% loss),
nic_2013-05-17-20-59-39 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-21-13-08 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-17-21-26-36 Sent = 200, Received = 196, Lost = 4 (2% loss),
nic_2013-05-17-21-40-13 Sent = 200, Received = 195, Lost = 5 (2% loss),
nic_2013-05-17-21-53-54 Sent = 200, Received = 190, Lost = 10 (5% loss),
nic_2013-05-17-22-07-58 Sent = 200, Received = 192, Lost = 8 (4% loss),
nic_2013-05-17-22-35-17 Sent = 200, Received = 197, Lost = 3 (1% loss),
nic_2013-05-17-23-02-14 Sent = 200, Received = 198, Lost = 2 (1% loss),
nic_2013-05-18-09-15-23 Sent = 200, Received = 198, Lost = 2 (1% loss),

Try a pathping from cmd and paste the results.

If our network was creating that level of packet loss we would be working all hours until it was fixed

If the packet loss returns as today rolls on, then the suggestion is that there is some congestion causing buffered packets and these may be delayed long enough to be considered lost by tools

The actual problem may be nothing at all to do with the ADSL segment

In reply to a post by ryant704:

Try a pathping from cmd and paste the results.

Good idea... I'll wait for a bit of packet loss to re-appear.

In reply to a post by MrSaffron:

If the packet loss returns as today rolls on, then the suggestion is that there is some congestion causing buffered packets and these may be delayed long enough to be considered lost by tools

The actual problem may be nothing at all to do with the ADSL segment

Well, it seems to have gone... snapshot

Whereas in the week it's been terrible... I'll keep an eye out to see if it comes back... but exchange congestion was something I was wondering about... the exchange is:Betley

Looks like packet loss has returned...

snapshot Graph

(The dip at 3am was when the ISP changed the ADSL profile from 6 meg down to 3 meg at the exchange, to see if that would help)


Pathping


Netgear detailed line stats

WinMtr stats