Ping time-outs, spikes, and unstable connection

felkup

Commendable
Feb 5, 2017
3
0
1,520
Dear all,
I have the following problem:
- Unreliable connection and many time-outs/data errors, even while surfing
- I narrowed it down to a latency issue: pinging my WiFi-router, the ping is between 3-10 ms, but every 10th attempt or so (no constant) is a ping over 2000 ms or a time-out. In every series of 30 pings there are 3-4 extreme spikes.

What I've tried:
- Update drivers in Windows 10 with manufacturer's drivers. No change.
- Change router channel. No change.
- Change location of the PC within the room. No change.
- Change USB WiFi dongle. The problem remains is the same, with two different D-Link DWA-172 and a TP-Link WN723N. All three work fine (no ping spikes) on another PC in the same room and on a laptop directly next to the PC in question.
- Change USB-slots. No change.
- Change b/g/n-protocol to b/g-only in the driver settings under Windows. That reduces the 2k+ ms spikes to c. 500 ms, which is still a lot.
- Do the ping-test on a live-Linux-system. No change.

So I figured, that the latency issue should be related to the USB-controller (on-board GIGABYTE GA-Z68M-D2H). A BIOS update didn't produce any change. Another PC with the same chipset, the same dongle and the same OS does not have the problem. Also, I have a USB-mouse/keyboard-dongle running on the same system without any lags. I am really running out of ideas here. Any suggestions anybody? Thanks a lot!
 
Solution
UPDATE: Got it. Was -what a relieve- software related: disabling a 3rd-party background-service (AUTODESK) solved the problem under Win10. I suspect latency issues on the LINUX live-system to have a different cause, e.g. driver incompatibility or the generally slow system. I leave the post for anybody who might run into the same problem.

felkup

Commendable
Feb 5, 2017
3
0
1,520
UPDATE: Got it. Was -what a relieve- software related: disabling a 3rd-party background-service (AUTODESK) solved the problem under Win10. I suspect latency issues on the LINUX live-system to have a different cause, e.g. driver incompatibility or the generally slow system. I leave the post for anybody who might run into the same problem.
 
Solution