Full Diagnostic Tree & Step-by-Step Overview
Plug your Ethernet cable securely into your computer and router/switch. Look closely at the small LED lights directly on the RJ45 Ethernet port. What is their status?
- Both LEDs are completely OFF (No link light on PC or Router)
- Solid Green/Amber link light is ON, but the Activity LED is NOT blinking, or Windows shows 'Unidentified Network' / 'No Internet Access'
- The link light is lit, but the connection constantly connects and disconnects every few seconds
What happens when you swap the Ethernet cable or try plugging into a different LAN port on your router?
- Swapping the cable restores the link light instantly
- Moving to a different LAN port on the router restores the link light
- The LEDs remain COMPLETELY OFF regardless of cable or router port used
Physical Wire Break, Pin Short, or Bad RJ45 Crimp
Solution:
Diagnostic Cause
Ethernet cables rely on eight twisted copper strands making physical contact with spring copper pins inside the RJ45 port. Broken retaining clip latches, kinked conductors, or internal strain-relief breaks stop the electrical physical layer (PHY) handshake.
Step-by-Step Fix
1. Discard the faulty cable.
2. Replace with a certified Cat5e, Cat6, or Cat6A patch cable.
3. Verify the RJ45 connector plastic latch clicks firmly into place on both the computer network card and the router port.
4. Avoid running Ethernet cables under heavy chair wheels, sharp door frames, or parallel to high-voltage AC power lines (which cause EMI noise).
Physical Port Damage, Blown Ethernet Transceiver, or Managed VLAN Isolation
Solution:
Diagnostic Cause
Individual Ethernet switch ports on home routers can fail due to localized power surges, electrostatic discharge (ESD), or misconfigured guest/VLAN port isolation.
Step-by-Step Fix
1. Leave the cable plugged into your PC and test LAN Ports 1 through 4 on the back of your router sequentially.
2. Log into your router's web admin console (192.168.1.1 or 192.168.0.1).
3. Navigate to Port Management or VLAN Settings and ensure the port is not assigned to an isolated Guest Network or disabled via parental controls.
4. If using an unmanaged desktop Ethernet switch, power-cycle the switch by unplugging its DC power adapter for 30 seconds.
Does the Ethernet adapter appear inside your operating system's hardware configuration (Device Manager / System Information)?
- No, the Ethernet controller is entirely MISSING from Device Manager
- Yes, it is listed, but has a yellow exclamation mark (!) or error code (Code 10, Code 43)
- Yes, it shows as 'Working Normally' in software, but physical LEDs remain dead
Onboard Network Interface Controller Disabled at Firmware Level
Solution:
Diagnostic Cause
If the Ethernet controller is missing completely from Device Manager (not even showing as an *Unknown Device*), the onboard NIC chip has likely been disabled inside your computer's UEFI/BIOS firmware or suffered total hardware failure.
Step-by-Step Fix
1. Restart your computer and repeatedly tap the BIOS key (Del, F2, or F12) during startup.
2. Navigate to Advanced > Integrated Peripherals or Onboard Devices Configuration.
3. Locate Onboard LAN Controller (or *Intel GbE LAN* / *Realtek PCIe GBE Controller*).
4. Change setting from *Disabled* to Enabled.
5. Press F10 to Save & Exit.
6. *If the option is enabled but missing in Windows, the onboard NIC chip has been damaged by a power surge; install a PCIe Ethernet card or USB-to-Ethernet adapter.*
Corrupted Driver Binary, Faulty Windows Update, or NDIS Hook Failure
Solution:
Diagnostic Cause
Windows Update frequently replaces stable network adapter drivers with generic WHQL drivers that lack proper hardware abstraction layer hooks for specific Realtek, Intel, or Marvell NIC revisions.
Step-by-Step Fix
1. Download the latest official Ethernet driver from your motherboard or laptop manufacturer (e.g., Intel I219-V / Realtek PCIe driver) onto a USB flash drive using another device.
2. Press Win + X and select Device Manager.
3. Expand Network adapters, right-click your Ethernet Controller > select Uninstall device.
4. Check Attempt to remove the driver for this device > click Uninstall.
5. Restart your computer.
6. Install the fresh manufacturer driver executable downloaded in Step 1.
Aggressive PCIe Power State & Green Ethernet PHY Sleep Lock
Solution:
Diagnostic Cause
Modern Ethernet chipsets use IEEE 802.3az Energy-Efficient Ethernet (EEE) and OS Power Management to shut off power to the port when idle. Aggressive power savings can prevent the port from waking up when a cable is connected.
Step-by-Step Fix
1. Open Device Manager (Win + X > *Device Manager*).
2. Expand Network adapters, right-click your Ethernet adapter > select Properties.
3. Go to the Power Management tab > uncheck Allow the computer to turn off this device to save power.
4. Go to the Advanced tab, scroll through the property list, and disable these features:
Energy-Efficient Ethernet -> *Disabled*Green Ethernet -> *Disabled*Power Saving Mode -> *Disabled*5. Click OK to apply.
IEEE 802.3ab Link Autonegotiation Failure or Flapping Connection
Solution:
Diagnostic Cause
Ethernet autonegotiation allows two network endpoints to agree on speed (10/100/1000 Mbps) and duplex mode. Slightly degraded cable pins or patch panel impedance mismatches cause the connection to rapidly flap (connect/disconnect) as it attempts to negotiate speed.
Step-by-Step Fix
1. Open Device Manager > expand Network adapters.
2. Right-click your Ethernet adapter > select Properties > click the Advanced tab.
3. Scroll down and select Speed & Duplex in the Property box.
4. Change the Value from *Auto Negotiation* to 1.0 Gbps Full Duplex.
5. If the link fails to stabilize, step down to 100 Mbps Full Duplex.
6. Click OK. *If 100 Mbps works but 1.0 Gbps drops, Pin 4, 5, 7, or 8 inside your cable or port is physically damaged (Gigabit requires all 8 wires; 100Mbps requires only 4).*
Open Command Prompt (`cmd`) and type `ipconfig`. What is listed under your Ethernet adapter's **IPv4 Address**?
- IP address starts with 169.254.x.x (APIPA Automatic Private IP Address)
- IP address is completely blank, or shows 0.0.0.0
- IP address shows a valid range (e.g., 192.168.1.x or 10.0.0.x), but says 'No Internet Access'
Router DHCP Server Unreachable / Windows APIPA Fallback
Solution:
Diagnostic Cause
An IP address starting with 169.254 means Windows successfully detected the physical cable connection, but failed to receive a dynamic IP lease response from the router's DHCP server.
Step-by-Step Fix
1. Open Command Prompt as Administrator (Win + X > *Terminal/CMD (Admin)*).
2. Force release and renew the DHCP configuration:
ipconfig /release press Enteripconfig /renew press Enter3. If ipconfig /renew hangs or errors with *'Unable to contact your DHCP server'*, verify whether a static IP or rogue third-party VPN network bridge is bound to the adapter:
Press Win + R, type ncpa.cpl > press Enter.Right-click Ethernet > Properties > TCP/IPv4 Properties.Ensure both Obtain an IP address automatically and Obtain DNS server address automatically are selected.
Corrupted TCP/IP Stack Registry Keys or Damaged Winsock LSP
Solution:
Diagnostic Cause
System crashes, unexpected power loss, or malware infections can corrupt the registry keys (HKLM\System\CurrentControlSet\Services\Tcpip) governing low-level network socket translation.
Step-by-Step Fix
1. Open Command Prompt as Administrator.
2. Run the following repair commands sequence:
netsh winsock reset *(Restores socket catalog to clean state)*netsh int ip reset *(Rewrites TCP/IP registry keys)*ipconfig /flushdns *(Purges OS DNS lookup table)*3. Restart your PC to allow system drivers to re-bind to clean sockets.
Address Resolution Protocol (ARP) Poisoning or Invalid Default Gateway Route
Solution:
Diagnostic Cause
Your PC holds a valid LAN IP, but traffic cannot pass through the local default gateway (router IP). This is caused by corrupted ARP tables (mapping local IP to MAC address) or manual default gateway misconfigurations.
Step-by-Step Fix
1. Open Command Prompt as Administrator.
2. Clear the local ARP cache by typing arp -d * and pressing Enter.
3. Ping your router's local IP address (e.g., ping 192.168.1.1).
4. If the ping times out, check if a manual default gateway was entered:
Run ncpa.cpl > Right-click Ethernet > Properties > TCP/IPv4 Properties.Click Advanced > Check Default gateways box.Remove any old or secondary default gateways listed.