For months, I've been using a wireless LAN USB driver on my desktop computer and had no problems with high latency or any errors in the network.
But then, I switched to using the ethernet port. It didn't work at first because my pc doesn't detect the connected cable, I found a (fix?) or a temporary solution to the problem. It's by configuring the LAN settings, specifically changing the speed and duplex to 10 Mbps full duplex and then it was fixed.
But after an hour or so, I would get disconnected alot, when I try to -ping in cmd, I often get a request timeout even with low ping.
The only temporary fix I find it resetting the speed and duplex again. But after a day, resetting the configuration doesn't work. I get a request timeout every 10 seconds or so.
32 Answers
We can try the following ways to troubleshoot the issue:
Try to change the network cable.
Port contact problem with the router or switch.
Try to update the NIC driver, if it does not work, maybe NIC aging causes this problem.
Other hardware issues.
If you manually configure the port to 10 Mbit/s full-duplex you've deactivated autonegotiation. This causes the switch port to use half-duplex(!), causing a duplex mismatch which will really suck performance-wise and cause lots of errors.
You need to use a proper cable. The cable needs to be at least Cat-5e. If you do have to manually configure down the NIC you either need to configure the switch port to 10M/full-duplex as well or (with an unmanaged switch) configure the NIC for 10M/half-duplex instead.
