A wired connection is supposed to be the reliable option, so when Ethernet starts dropping out — a brief "no internet" toast notification, a stuttering video call, or a games console booting to an error — it's often more confusing to diagnose than Wi-Fi problems. This guide walks through the physical, driver, and configuration causes in the order you should actually check them.

Step 1: Confirm It's Really the Wired Connection

Before chasing cables, rule out the obvious:

  1. Check whether Wi-Fi on the same device also drops at the same time — if so, the problem is upstream (router, ISP, or power), not the Ethernet link itself.
  2. Look at your router or switch's WAN/Internet light — if that flickers or drops when your Ethernet does, your broadband line itself is at fault, not the cable to your PC.
  3. Note the pattern: does it drop at a regular interval (every few minutes — suggests power saving or a driver issue), randomly (suggests a cable or port fault), or only under load (large downloads, gaming — suggests duplex mismatch or a failing NIC)?

Step 2: Check the Physical Cable and Ports

Ethernet problems are physical far more often than people expect.

  1. Inspect both ends of the cable for bent or missing pins, and check the little plastic locking clip hasn't snapped off — a cable that isn't clicking firmly into place will work intermittently and drop under vibration or heat.
  2. Try a different cable. Cat5e or Cat6 cables are cheap, and a damaged one (kinked, crushed under furniture, chewed by a pet) is one of the single most common causes of intermittent drops.
  3. Try a different port on the router or switch. A failing port on ageing networking hardware will drop connections intermittently before failing completely.
  4. Check cable length and routing — Ethernet is rated to 100 metres, but a cable run alongside mains power cables or through areas with electrical interference (near a boiler, large motor, or fluorescent light fitting) can suffer signal degradation well within that limit.
  5. If you're using any coupler, wall-mounted socket, or patch panel, check those connections too — a loose crimp at a wall plate is a very common intermittent fault.

Pro tip: Swap the suspect cable with one you know works from another device, and swap the ports too. If the drops follow the cable, replace it — they cost very little and testing is the fastest way to rule this out for good.

Step 3: Check for Duplex Mismatches and Speed Negotiation Issues

Ethernet devices "negotiate" a speed and duplex setting (half or full) automatically. A mismatch here can cause connections that work but drop or slow down under load.

  1. On Windows, open Device Manager > Network adapters, right-click your Ethernet adapter, and choose Properties > Advanced.
  2. Find Speed & Duplex in the list and set it to Auto Negotiation if it isn't already — a manually forced setting that doesn't match the switch or router's setting is a classic cause of dropped or throttled connections.
  3. If auto-negotiation is already set and problems persist, try manually forcing both the PC and the router/switch to the same fixed speed (e.g. 100 Mbps Full Duplex) as a diagnostic test — if this fixes the drops, the auto-negotiation itself is faulty and pointing to ageing hardware on one end.

Step 4: Update or Roll Back the Network Adapter Driver

  1. Open Device Manager, expand Network adapters, right-click your Ethernet controller (commonly Realtek, Intel, or Killer), and select Update driver.
  2. Choose Search automatically for drivers, or better, download the latest driver directly from your motherboard or laptop manufacturer's support page for a more current version than Windows Update typically offers.
  3. If the drops started right after a driver or Windows update, try Roll Back Driver (same Properties window, Driver tab) to undo the change.
  4. Check Power Management on the same adapter's Properties: untick "Allow the computer to turn off this device to save power" — this setting causes exactly the kind of intermittent, seemingly random Ethernet drops that are maddening to diagnose, especially on laptops.

Step 5: Rule Out Router or Switch Overload

  1. If you have many devices connected through a single switch or a router with limited ports, an ageing or underpowered switch can drop connections under combined load.
  2. Check the switch or router for warmth or dust build-up — networking hardware crammed into an enclosed media cabinet can overheat and behave erratically, including dropping ports.
  3. Restart the router and any intermediate switches — a simple power cycle clears a surprising number of transient faults caused by memory leaks in cheap networking hardware.
  4. If you're daisy-chaining several switches, try connecting the affected device more directly to rule out a faulty link further up the chain.

Step 6: Check for Software and Security Conflicts

  1. Temporarily disable third-party antivirus or firewall software to test — some security suites' network filtering drivers are known to cause intermittent connection drops, particularly after a buggy update.
  2. Check for VPN client software running in the background, even if not actively connected — some VPN network adapters interfere with normal traffic.
  3. Run ipconfig /flushdns and netsh winsock reset in an elevated Command Prompt, then restart — this clears a corrupted network stack that can cause connections to silently fail and recover.

Step 7: Use Event Viewer to Catch the Pattern

For persistent, hard-to-pin-down drops:

  1. Open Event Viewer (search from the Start menu).
  2. Navigate to Windows Logs > System.
  3. Filter for Event ID 27 (network disconnect events) or look for entries from source "e1dexpress," "RTL8168," or similar, which name your adapter around the time of a known drop.
  4. Note the exact time of the next drop and cross-reference it against the log — this often reveals whether it coincides with a Windows Update, a sleep/wake cycle, or a driver crash.

Warning: Before assuming a hardware fault and buying replacement equipment, always test with a known-good cable in a known-good port first — this single step resolves the majority of "faulty Ethernet" cases and costs nothing.

When to Replace Hardware

  • If a specific cable or port fails the swap test consistently, replace that cable or use a different port permanently.
  • If a network adapter shows driver crashes in Event Viewer repeatedly even after reinstalling drivers, and the issue follows the PC to a different cable and port, the onboard NIC itself may be failing — a USB-to-Ethernet adapter (£10-£15) is a cheap way to confirm this without a motherboard replacement.
  • If your router or switch is more than 6-7 years old and shows physical wear, overheating, or repeated port failures, replacing it resolves a wide range of these symptoms at once.

Working through cabling and ports first, then drivers and power settings, and only then hardware replacement will resolve the overwhelming majority of "random" Ethernet drops without unnecessary spending.

Was this guide helpful? Explore more Networking & Wi-Fi Issues guides, or browse all Operating System & Software articles.