A Windows PC that suddenly stops sending Ethernet packets is typically caused by a corrupted network stack, disabled network adapters, or IP configuration conflicts. The most effective immediate fix involves resetting the TCP/IP stack and clearing the DNS cache via the Command Prompt, followed by verifying that the physical link light is active and the adapter is enabled in Device Manager.
Verify Physical Connectivity and Link Status
Before diving into software diagnostics, ensure the hardware layer is functioning correctly. Ethernet issues often stem from loose cables or switch port failures rather than OS-level bugs. Check the RJ45 connector at both ends of the cable to ensure it clicks securely into place. Look at the small LED indicators on the Ethernet port; a solid green or amber light usually indicates a valid physical link, while blinking suggests data activity. If there are no lights, try a different cable or move the connection to another port on your router or switch. This simple step eliminates physical layer faults before you proceed with complex software troubleshooting.
Reset the Network Stack via Command Prompt
Corrupted system files related to networking can prevent packet transmission entirely. You can force Windows to rebuild these configurations using built-in command-line tools. Open the Start menu, type
cmd, right-click "Command Prompt," and select "Run as administrator." In the elevated window, execute the following commands one by one, pressing Enter after each:
netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
The
netsh int ip reset command resets the TCP/IP stack to its default state. The
netsh winsock reset repairs the Winsock catalog, which handles network protocol requests. Releasing and renewing the IP address forces the computer to request a fresh lease from your DHCP server. Flushing the DNS clears outdated or incorrect domain name resolution records. After running these commands, restart your computer immediately to apply the changes.
Check Adapter Settings and Driver Status
If the stack reset did not resolve the issue, the network adapter itself may be disabled or malfunctioning. Press
Win + X and select "Device Manager" from the menu. Expand the "Network adapters" section and locate your Ethernet controller. Right-click the adapter and select "Properties." Navigate to the "Power Management" tab and uncheck "Allow the computer to turn off this device to save power." Power saving features can sometimes cause the card to enter a deep sleep state that fails to wake up properly.
Next, check for driver errors. If you see a yellow exclamation mark next to the adapter, the driver is likely corrupted. Right-click the device and select "Update driver," then choose "Search automatically for updated driver software." Alternatively, visit your motherboard or laptop manufacturer's website to download the latest LAN driver manually. Installing the correct driver ensures compatibility with the current version of Windows and resolves underlying communication errors.
Disable Conflicting Software and Firewalls
Third-party security software can occasionally block outgoing Ethernet packets if it misinterprets traffic as malicious. Temporarily disable any third-party antivirus or firewall applications to test if they are the culprit. Additionally, Windows Update or recent system patches might have introduced a conflict. If the issue started recently, consider rolling back the network adapter driver to a previous version through Device Manager properties under the "Driver" tab.
For users who share their internet connection, such as those setting up a hotspot, ensure that Internet Connection Sharing (ICS) is configured correctly. Improper ICS settings can interfere with standard Ethernet connectivity. Refer to our guide on
Sharing Ethernet Internet Connection via WiFi Hotspot on a Windows PC without a WiFi Card to understand how sharing interfaces interact with primary network stacks.
Advanced Diagnostics with Ping and Tracert
If basic fixes fail, use diagnostic tools to pinpoint where the packet loss occurs. Open Command Prompt again and run
ping 127.0.0.1. A successful reply confirms the TCP/IP stack is working locally. Next, ping your default gateway (e.g.,
ping 192.168.1.1). Failure here indicates a local network issue, possibly related to IP conflicts or subnet mask errors. If the gateway responds but external sites like
ping 8.8.8.8 do not, the problem lies with your ISP or router configuration. Use
tracert 8.8.8.8 to identify the specific hop where packets stop traveling.
Frequently Asked Questions
Why does my Ethernet light stay off even though the cable is plugged in?
This usually indicates a physical layer failure, such as a broken cable, a faulty switch port, or a damaged NIC. Try swapping the cable and testing a different port on the router first. If the light remains off, the network interface card may be physically damaged or disabled in the BIOS.
Can disabling IPv6 fix sudden Ethernet connectivity loss?
Yes, conflicting IPv6 configurations can sometimes prevent proper packet routing. In Network Connections, right-click your Ethernet adapter, select Properties, and uncheck "Internet Protocol Version 6 (TCP/IPv6)." Apply the changes and test the connection. This forces the system to rely solely on IPv4, which is more universally supported in legacy environments.
What should I do if ipconfig shows an APIPA address like 169.254.x.x?
An APIPA address means the PC failed to obtain an IP from the DHCP server. This often happens due to router glitches or IP exhaustion. Restarting your router and modem will clear stale leases. On the PC, running
ipconfig /release followed by
ipconfig /renew forces a fresh request for an address.
Does enabling Explicit Congestion Notification (ECN) help with packet loss?
ECN can improve performance on high-latency connections but is rarely the cause of total packet silence. It is primarily used to debug slow ISP connections rather than complete outages. For general Ethernet troubleshooting, focus on stack resets and driver updates before modifying congestion control settings. See our article on
Debugging Slow ISP Connection on Windows Machine: Enabling Explicit Congestion Notification (ECN) for details on when ECN is appropriate.
How do I know if a firewall is blocking my Ethernet packets?
Temporarily disable third-party firewalls and the Windows Defender Firewall to test connectivity. If the connection works with the firewall off, create a new inbound/outbound rule to allow your specific application or service. Be cautious when disabling firewalls permanently, as it exposes your system to network threats.