Ethernet connection not working on Windows
Diagnose wired networking from cable and link state through addressing.
- Updated
- September 3, 2026
- Reading time
- 7 min read
- Windows support
- Windows 11 · Windows 10
Quick diagnosis
Diagnose wired networking from cable and link state through addressing. The key distinction is whether “Unidentified network” occurs by itself or together with “no link lights.” That difference helps separate bad cable or port from disabled adapter.
Symptoms
- Unidentified network
- No link lights
Likely causes
- Bad cable or port
- Disabled adapter
- Failed DHCP
Quick reversible checks
- Try a known-good cable and port
- Disable Wi-Fi during testing
Establish the scope
Confirm when unidentified network and whether no link lights. Note the exact time and the last relevant change, then compare the closest known-good device, account, connection, or application using the same task.
Apply the safer fix first
Confirm link lights and an enabled adapter. Use ipconfig /all; Media disconnected means no link, while 169.254 addressing suggests DHCP failure.
- Record the current state related to try a known-good cable and port.
- Apply the narrow change, then check whether unidentified network.
- Continue only if the result still points toward disabled adapter.
Investigate the cause
After recording static settings, renew DHCP. Update the LAN driver from the computer or motherboard maker if Device Manager reports a fault.
Protect the recovery path
Before work that could affect network & internet, protect relevant files and sign-in or recovery credentials. Keep the original error wording and the results involving bad cable or port, disabled adapter, failed dhcp for support.
Verification
- Repeat the affected task under the same conditions used to confirm unidentified network. Confirm the symptom is gone, not merely that a Windows status label changed.
- Repeat the relevant connection, startup, sign-in, sleep, application, or device transition and specifically check whether no link lights.
When to stop
Do not continue with broader resets when known-good cables and ports show no link or the socket is damaged. Preserve the observations already collected and use the device maker, network administrator, Microsoft support, a qualified repair technician, or data-recovery help according to the evidence.
Review the safe troubleshooting workflow before any broader recovery step.