Network & Internet

Ethernet connection not working on Windows

Diagnose wired networking from cable and link state through addressing.

Updated
September 18, 2026
Reading time
7 min read
Windows support
Windows 11 · Windows 10

Quick diagnosis

Diagnose wired networking from cable and link state through addressing.

Symptoms

  • Unidentified network
  • No link lights

Likely causes

  • Bad cable or port
  • Disabled adapter
  • Failed DHCP

Quick reversible checks

  1. Try a known-good cable and port
  2. Disable Wi-Fi during testing

Establish the scope

Separate a missing physical link from a connected adapter with unusable addressing. Compare a known-good cable and router port first, then inspect the active Ethernet adapter. A valid-looking IP configuration still needs a reachability test; it does not prove that the router has internet access.

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.

Investigate the cause

If the adapter uses DHCP and has a working link, follow the related release/renew reference before requesting a new lease. Do not apply renewal to intentional static addressing. Update the LAN driver from the computer or motherboard maker if Device Manager reports a fault.

Protect the recovery path

Keep another access method before disabling Wi-Fi. Do not release a lease during a remote session or replace intentional static addressing.

Verification

  • Confirm a stable wired link and the intended IP configuration while Wi-Fi is disabled for the comparison.
  • Open the original service over Ethernet, then restore any temporary Wi-Fi setting.

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.