Ethernet that keeps disconnecting — cutting out for a few seconds then reconnecting, or dropping completely until unplugged and replugged — has a specific pattern that usually reveals the cause within minutes of looking at the right information. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
Run ping 192.168.1.1 -t and ping 8.8.8.8 -t simultaneously in two Command Prompt windows. When the next disconnection happens: check which ping stopped working. If both stop simultaneously: your connection to the router failed — check the cable or router. If 8.8.8.8 stops but 192.168.1.1 continues: the router has internet but something’s wrong at the ISP level. If both continue: the Ethernet appears to have reconnected already or the disconnection is in a specific application, not the adapter.
The dual-ping test takes 2 minutes to set up and immediately tells you whether the disconnection is local (cable, adapter, router) or upstream (ISP, modem).
Power management — the most common software cause
Windows’ USB-style selective suspend also applies to Ethernet adapters. The NIC gets powered down during idle periods, fails to wake correctly, and drops the connection. The reconnection sound plays 30–60 seconds later when Windows detects the lost connection and re-initialises the adapter.
Device Manager → Network Adapters → right-click Ethernet adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also Advanced tab → look for “Energy Efficient Ethernet” or “Green Ethernet” → Disable both. These power-saving features reduce NIC power during inactivity in ways that can cause connection drops. Apply all three → restart → test for 30 minutes of inactivity.
The cable. Always check the cable.
Ethernet cables fail more often than software problems cause disconnections. A cable with a damaged wire, a connector with a bent pin, or a cable that’s too long (over 90 metres for Cat5e/Cat6) causes intermittent disconnections that look like driver or router problems. The disconnection is real-time and unrelated to software state.
Swap the cable. Entirely. Don’t just reseat the ends — replace the cable with a known-good one. If disconnections stop immediately: the original cable was the problem. This is the fix that feels too simple but solves the problem a significant fraction of the time.
Driver update or rollback
Ethernet adapter drivers from Windows Update are often generic versions that handle power states less gracefully than manufacturer drivers. Disconnections that started after a Windows Update usually indicate a driver regression.
Device Manager → Ethernet adapter → Properties → Driver tab → Roll Back Driver if available and the problem started after an update. Otherwise: download the current Ethernet driver from the laptop or motherboard manufacturer’s support page. Realtek and Intel NIC drivers from manufacturer support pages are more thoroughly tested than what Windows Update distributes.
Advanced NIC settings
Device Manager → right-click Ethernet adapter → Properties → Advanced tab. Several settings here affect connection stability:
- Speed and Duplex: should be “Auto Negotiation” — if manually set, a mismatch with the router/switch causes intermittent drops
- Interrupt Moderation Rate: try “Low” if currently on “Adaptive” — aggressive moderation occasionally causes connection timing issues
- IPv4 and IPv6 Checksum Offload: should be Enabled — disabling these pushes checksum work to the CPU which can create timing issues under load
- Wake on LAN / Wake on Magic Packet: can cause the adapter to enter partial sleep states — try disabling if disconnections happen specifically when the machine is idle
Router and switch port issues
A specific router port may be failing. Try a different port on the router or switch. If the disconnections stop: the original port was faulty. Most consumer routers have 4 ports — ports develop hardware issues over time, particularly the most-used ones.
Also: some managed switches have loop protection or STP (Spanning Tree Protocol) configured to disable ports that appear to be causing loops. If the Ethernet disconnects and takes 10–30 seconds to reconnect (longer than a simple cable reconnect): STP port recovery timeout may be the cause. Check the switch’s STP configuration if applicable.
IP address lease renewal causing brief gaps
DHCP leases expire and need to be renewed. During the renewal process — which normally takes less than a second — the connection is technically valid but momentarily transitions. On some router/adapter combinations: this transition causes applications to lose their connections briefly.
In the router admin panel: increase the DHCP lease time (often 1 hour by default on home routers — increase to 24 hours or longer for desktop machines that are always on the same network). Or set a static IP for the machine to eliminate DHCP renewal entirely. Settings → Network and internet → Ethernet → your connection → IP settings → Manual → configure a static IP outside the DHCP range.
Network stack reset for software-accumulated issues
netsh winsock reset
netsh int ip reset
ipconfig /flushdnsAdministrator Command Prompt → run all three → restart. Resolves disconnections caused by accumulated TCP/IP stack state corruption that normal driver updates don’t clear. Particularly effective when disconnections started after VPN software installation or after changing network security software.
Our guide on Ethernet no valid IP covers the DHCP failures that accompany some disconnection patterns. For router-level firmware and configuration issues, our router disconnecting guide covers the upstream causes that affect all devices simultaneously rather than just the Ethernet-connected machine. Microsoft’s Ethernet adapter documentation covers the NIC reset commands and the ETL tracing approach that Microsoft support uses for persistent adapter disconnections.
Link speed downgrade and its disconnect pattern
Ethernet adapters negotiate connection speed with the router/switch automatically. Marginal cables sometimes negotiate at 100Mbps rather than 1000Mbps — and at that lower negotiated speed, the connection is stable but slow. More problematically: cables that can barely maintain any connection may repeatedly fail negotiation and renegotiate, appearing as brief disconnections followed by reconnection (sometimes at a different speed each time).
Settings → Network and internet → Ethernet → Properties → look at “Link speed (Send/Receive).” If it shows 100/100 Mbps when you expect Gigabit: the cable or port is limiting the connection. In Device Manager → Advanced tab → Speed and Duplex: try manually setting “1 Gbps Full Duplex” — if it connects, the cable supports Gigabit but negotiation was failing. If setting 1 Gbps causes disconnections while Auto Negotiation was stable at 100Mbps: the cable is the bottleneck and should be replaced with Cat5e or Cat6.
USB-to-Ethernet adapter specific issues
Laptops without built-in Ethernet using USB adapters have additional failure modes beyond regular NIC issues. USB Ethernet adapters depend on USB power delivery, which Windows can cut through selective suspend. They also share USB bandwidth with other connected devices and can disconnect when USB bandwidth is saturated by other devices.
For USB Ethernet adapters: ensure the power management settings from the first fix apply to the USB adapter entry in Device Manager (it appears under both Network Adapters and USB devices — apply the power management fix at both levels). Also ensure the adapter is in a USB 3.0 port rather than USB 2.0 — Gigabit Ethernet over USB 2.0 saturates the USB bus and causes intermittent drops under load.
Duplex mismatch — the silent killer of Ethernet stability
Auto-negotiation works correctly when both sides properly implement the auto-negotiation protocol. When one side is manually configured (the router or switch port is set to 100Mbps Full Duplex without auto-negotiation) and the other side is set to Auto (the NIC), the auto-negotiating side guesses and sometimes guesses wrong — defaulting to half duplex when the other side is full duplex. Half-duplex at Gigabit speeds is unstable and causes frequent disconnections under load.
Both sides should be set to Auto Negotiation for reliable operation. In Device Manager → Advanced → Speed and Duplex: confirm it’s “Auto Negotiation.” For managed switches where the port is manually configured: either reconfigure the port to auto-negotiate, or match the NIC setting manually to what the switch port expects. Mismatched negotiation causes disconnections that look like cable or driver problems but are actually protocol-level conflicts between the two ends of the connection.
Event Viewer for Ethernet disconnection events
Event Viewer → Windows Logs → System → filter Source “e1iexpress” or “Netwtw” or “tcpip” (the event source depends on the NIC vendor). Also look for “NDIS” events — NDIS is Windows’ network driver interface and logs every adapter state change. An “NDIS: miniport…” event at the time of disconnection shows the exact adapter state transition and error code that caused the disconnect.
Common NDIS disconnect patterns: “The network link was lost” — physical layer event (cable, switch port). “The NIC driver reported an internal error” — driver or firmware issue. “Link speed change” at the time of disconnect — negotiation failure. Each tells you a different thing about where to look.
Sleep and wake Ethernet drops
Ethernet that disconnects specifically when the machine wakes from sleep is a power management issue in the adapter’s sleep state handling. During sleep, the NIC may enter a low-power state that takes 5–30 seconds to fully resume on wake. During that resume period, applications time out their connections because the adapter isn’t yet responsive.
In addition to the Device Manager power management fix: Control Panel → Power Options → active plan → Change plan settings → Change advanced power settings → PCI Express → Link State Power Management → Off. PCIe power management affects the physical link between the NIC and the PCIe bus — disabling it prevents the NIC from entering a sleep state on the PCIe bus that requires full reinitialisation on wake.
Switch negotiation and Windows’ network stack after restart
After a Windows restart: the NIC comes up before the TCP/IP stack is fully initialised. During those first 2–3 seconds after the NIC comes up, the switch detects the link and starts forwarding traffic. But Windows isn’t ready to respond yet, and some switches interpret the lack of response as a link instability event — resetting the port and forcing renegotiation. The result: Windows boots, shows “Network connected” briefly, then disconnects for 5–10 seconds before reconnecting stably.
This is a switch configuration issue rather than a Windows problem. Managed switches: enable “portfast” or “edge mode” on the port connecting the Windows machine — this skips the STP learning period and connects the port immediately rather than waiting for the STP protocol to determine if a loop exists. Unmanaged switches don’t have this configuration option, but the delay is usually under 15 seconds and resolves automatically.
Practically, the most reliable sequence for unknown Ethernet disconnections: (1) Set up dual-ping monitoring to characterise the disconnect pattern. (2) Swap the cable entirely. (3) Apply NIC power management fixes and disable Energy Efficient Ethernet. (4) Try a different router port. (5) Update the NIC driver from the manufacturer’s site. These five steps cover the causes of over 90% of Ethernet disconnections. The IP lease, duplex mismatch, STP, and PCIe power management fixes are for the remaining cases where the first five haven’t resolved it — they’re important to know but apply to a minority of situations.
Lightning and electrical surge damage
Ethernet cables conduct electricity. A nearby lightning strike or electrical surge on the network line — through the cable, via the router, or directly on a cable run that goes outside — can damage the NIC’s Ethernet interface while leaving the rest of the machine functional. The NIC works initially but becomes intermittently unstable as the damaged components degrade with use and temperature changes.
Signs: disconnections started after a storm or power event. The NIC’s Ethernet port may feel slightly warm compared to before. The disconnections worsen over time rather than staying constant. A USB Ethernet adapter (plugging into USB rather than the built-in RJ45 port) as a temporary replacement confirms whether the built-in NIC is the issue — if the USB adapter is stable, the built-in port was damaged.
When all fixes fail: hardware verification
If disconnections persist through all software fixes, cable replacement, and different router ports: test with a USB Ethernet adapter for a few hours. If the USB adapter maintains a stable connection while the built-in NIC doesn’t: the built-in NIC hardware has an issue that software can’t resolve. Options: continue using the USB adapter as a replacement, have the NIC hardware examined by a technician, or in the case of desktop machines, install a PCIe Ethernet card as a replacement NIC. For laptops, a USB adapter is often the most practical and cost-effective permanent solution for a failing built-in NIC.
One last thing worth checking for machines that have had Ethernet disconnections for a long time: the RJ45 connector on the back of the machine and the jack on the cable. The plastic tab that locks the connector in place can break off — the connector stays seated most of the time but the slightest vibration (opening a drawer nearby, a truck driving past) causes it to partially unseat and briefly disconnect. A cable with an intact locking tab and a port where the connector clicks firmly into place is basic but often overlooked. Wiggling the cable at the connector point while watching the dual-ping output immediately confirms whether the physical connection is the problem. You might also run into VPN Keeps Disconnecting.
