Packet loss on wired

freddukes · Sep 17, 2014

Hi Guys,

This is a weird one, I've never seen this issue before. I'm currently connected to an EE Brightbox router, and I'm having trouble with packet loss (around 25%) whilst connected through ethernet. Wi-fi works perfectly on different devices. I've tried eithernet through multiple devices, different adapters, reinstalling firmware / drivers; the issue seems to persist.

It's noticeable whilst I'm attempting to browse the web. Through ethernet, the page fails to load about 50% of the time, and the other 50% takes an extremely long time to load (google home page takes about 30 seconds to load through ethernet, about a second on wifi).

Below are two results of "pathping 8.8.8.8":

Wifi:

C++:

Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Steven-XPS.default [192.168.1.219]
                                0/ 100 =  0%   |
  1    7ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2  448ms     1/ 100 =  1%     1/ 100 =  1%  213.1.113.110
                                0/ 100 =  0%   |
  3  525ms     0/ 100 =  0%     0/ 100 =  0%  213.1.128.190
                                0/ 100 =  0%   |
  4  523ms     0/ 100 =  0%     0/ 100 =  0%  213.1.78.34
                                0/ 100 =  0%   |
  5  526ms     0/ 100 =  0%     0/ 100 =  0%  87.237.20.128
                                0/ 100 =  0%   |
  6  522ms     0/ 100 =  0%     0/ 100 =  0%  72.14.223.2
                                0/ 100 =  0%   |
  7  527ms     0/ 100 =  0%     0/ 100 =  0%  209.85.246.244
                              100/ 100 =100%   |
  8  ---     100/ 100 =100%     0/ 100 =  0%  209.85.253.94
                                0/ 100 =  0%   |
  9  ---     100/ 100 =100%     0/ 100 =  0%  72.14.232.134
                                0/ 100 =  0%   |
 10  ---     100/ 100 =100%     0/ 100 =  0%  209.85.250.165

Trace complete.



C:\Windows\System32>ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=687ms TTL=47
Reply from 8.8.8.8: bytes=32 time=568ms TTL=47
Reply from 8.8.8.8: bytes=32 time=628ms TTL=47
Reply from 8.8.8.8: bytes=32 time=648ms TTL=47
Reply from 8.8.8.8: bytes=32 time=590ms TTL=47
Reply from 8.8.8.8: bytes=32 time=536ms TTL=47
Reply from 8.8.8.8: bytes=32 time=624ms TTL=47
Request timed out.
Reply from 8.8.8.8: bytes=32 time=522ms TTL=47
Reply from 8.8.8.8: bytes=32 time=513ms TTL=47
Reply from 8.8.8.8: bytes=32 time=623ms TTL=47
Reply from 8.8.8.8: bytes=32 time=637ms TTL=47
Reply from 8.8.8.8: bytes=32 time=507ms TTL=47
Reply from 8.8.8.8: bytes=32 time=560ms TTL=47
Reply from 8.8.8.8: bytes=32 time=481ms TTL=47
Reply from 8.8.8.8: bytes=32 time=568ms TTL=47
Reply from 8.8.8.8: bytes=32 time=614ms TTL=47
Reply from 8.8.8.8: bytes=32 time=551ms TTL=47
Reply from 8.8.8.8: bytes=32 time=550ms TTL=47
Reply from 8.8.8.8: bytes=32 time=602ms TTL=47

Ping statistics for 8.8.8.8:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 481ms, Maximum = 687ms, Average = 579ms

C:\Windows\System32>

Ethernet:

C++:

Computing statistics for 25 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Steven-XPS.default [192.168.1.105]
                                0/ 100 =  0%   |
  1    1ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1

Trace complete.


C:\Windows\System32>ping 8.8.8.8 -n 20

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Reply from 8.8.8.8: bytes=32 time=33ms TTL=46
Reply from 8.8.8.8: bytes=32 time=34ms TTL=46
Reply from 8.8.8.8: bytes=32 time=36ms TTL=46
Reply from 8.8.8.8: bytes=32 time=39ms TTL=46
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=35ms TTL=46
Reply from 8.8.8.8: bytes=32 time=64ms TTL=46
Reply from 8.8.8.8: bytes=32 time=51ms TTL=46
Reply from 8.8.8.8: bytes=32 time=50ms TTL=46
Reply from 8.8.8.8: bytes=32 time=43ms TTL=46
Request timed out.
Reply from 8.8.8.8: bytes=32 time=40ms TTL=46
Reply from 8.8.8.8: bytes=32 time=34ms TTL=46
Reply from 8.8.8.8: bytes=32 time=50ms TTL=46

Ping statistics for 8.8.8.8:
    Packets: Sent = 20, Received = 12, Lost = 8 (40% loss)
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 64ms, Average = 42ms

I've tried restarting the router, but nothing changed. These tests were taken from my laptop on Windows 8, but I've tried on my desktop which is running windows 7 and I get almost identical results. I've reset to factory defauts, still nothing. Can any of you suggest anything, or is this going to be an engineer callout job?

Cheers,

-Steven

bill001g · Sep 17, 2014

The latency is strange.

500ms if outrageous that is what you get on a satellite. What is strange is normally you would see that on the first hop. I would suspect 192.168.1.1 is your router and the 213.1.113.110 is the first router in the ISP but this makes no sense. Once you get to the router there should be no difference in the latency beyond that.

The difference in the loss is likely due the high delays. pretty much since the ping takes so much longer the total number of pings you run say in a minute is much less for the 500ms ones. It may just be that you are seeing more loss because you are sending more total pings packets.

I would ping the first hop past your router. If you see errors on this from either connection then you need to get the ISP to fix it. I can't imagine what would introduce 500ms of delay. You see delays like that on a satellite or maybe a cellular broadband connection.

freddukes · Sep 17, 2014

bill001g :

Thank you for your reply. You're right, I think someone else on my network must have been downloading at the same time (student accomodation). Just tried again on wireless and got similar results in speed to ethernet, only without the packet loss:

Wi-fi

C++:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=29ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=37ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=33ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48
Reply from 8.8.8.8: bytes=32 time=29ms TTL=48
Reply from 8.8.8.8: bytes=32 time=29ms TTL=48
Reply from 8.8.8.8: bytes=32 time=30ms TTL=48

Ping statistics for 8.8.8.8:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 37ms, Average = 30ms

Ethernet

C++:

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=33ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Request timed out.
Reply from 8.8.8.8: bytes=32 time=31ms TTL=47
Reply from 8.8.8.8: bytes=32 time=31ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=31ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Request timed out.
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Request timed out.
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Request timed out.
Request timed out.

Ping statistics for 8.8.8.8:
    Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 33ms, Average = 31ms

bill001g · Sep 17, 2014

You would think it would be the reverse. Normally this would be a bad cable but since you have tried another it get tough. Generally then you are looking for something like a half duplex connection. You could check the setting in the nic and make sure it is set to speed and duplex auto. Other than that you start getting into strange things like damaged jacks on the pc or the router.

I suppose it would be very helpful if you could take the machine to someplace else and plug it into a different router. That would confirm you pc doesn't have a issue.

You would be best off pinging the router ip with a large packet size just to confirm it is really between the router and the pc. If it would only happen when you ping stuff from a wired pc to ip in the internet then I have no clue. It would either be a bug in the router or it would be some kind of firewall or QoS limitation that was configured.

freddukes · Sep 20, 2014

Just as a follow up to this, it ended up being a faulty port in my room that I was connecting through. I had engineers replace the port and it solved all issues. Thank you for the help!

Search

Packet loss on wired

freddukes

Honorable

bill001g

Titan

freddukes

Honorable

bill001g

Titan

freddukes

Honorable

TRENDING THREADS

Latest posts

Moderators online

Share this page