Ethernet Connected But No Link Detected

Step 1: Check the interface status in the OS

# Linux — show interface state (look for "NO-CARRIER" or "state DOWN")
ip link show eth0
# Expected output for connected: <BROADCAST,MULTICAST,UP,LOWER_UP>
# Problem output: <BROADCAST,MULTICAST> state DOWN  (no LOWER_UP = no link)

# Check for more detail
ethtool eth0
# Look for:
#   Link detected: yes   (healthy)
#   Link detected: no    (no physical link)

# macOS
ifconfig en0 | grep "status"
# "status: active" = link present
# "status: inactive" = no link

# Windows
netsh interface show interface
# Administrative State: Enabled, State: Connected (healthy)
# Administrative State: Enabled, State: Disconnected (no link)

Step 2: Test the cable

# If a cable tester is available:
# - Remove cable from both ends
# - Connect to the tester
# - A working Cat5e/Cat6 cable shows continuity on all 8 pins (1-1, 2-2, ... 8-8)
# - A wiring fault shows missing or crossed pins

# Without a tester, try these quick tests:
# 1. Swap the cable with a known-good cable
# 2. Try a shorter cable (under 5 meters) to eliminate length as a variable
# 3. Check for visible damage: kinks, crushed sections, bent RJ45 pins

Step 3: Check the switch port

# Try plugging the cable into a different port on the switch
# Look at the switch LED for the port you just moved to — does it light up?

# On a managed switch, check port status via CLI:
# Cisco IOS:
show interfaces FastEthernet0/1 status
show interfaces GigabitEthernet0/1

# Look for:
# "connected" or "notconnect" status
# "err-disabled" = port disabled by switch due to error (violation, loop, etc.)

Step 4: Check for auto-negotiation issues

# Linux — check if auto-negotiation is enabled and what was negotiated
ethtool eth0
# Look for:
#   Supported link modes:    10baseT/Half 10baseT/Full 100baseT/Full 1000baseT/Full
#   Advertised link modes:   (same as above if auto-neg is on)
#   Auto-negotiation: on
#   Speed: 1000Mb/s
#   Duplex: Full
#   Link detected: yes

# Try forcing speed/duplex to bypass auto-negotiation issues
sudo ethtool -s eth0 speed 100 duplex full autoneg off

Step 5: Test with a different NIC

If all cables and switch ports are verified good but still no link:

• Connect via USB-to-Ethernet adapter to rule out a faulty built-in NIC
• On a desktop, try a PCIe network card in a different slot
• Check Device Manager (Windows) or lspci (Linux) to verify the NIC is recognized by the OS

Step 6: Check for disabled interface in OS

# Linux — bring up a DOWN interface
sudo ip link set eth0 up

# Verify it came up
ip link show eth0

# Windows — enable a disabled adapter
netsh interface set interface "Ethernet" admin=enabled

# macOS (System Settings > Network > Ethernet > Connect)

Solution A: Replace the cable (most common fix)

1. Use a cable tester to verify the existing cable or skip this step and just swap it
2. Replace with a Cat5e or Cat6 cable of known-good quality
3. Ensure the new cable is under 100 meters for reliable Gigabit Ethernet
4. Verify the link light appears on both ends after replacing

Solution B: Move to a different switch port

1. Unplug the cable from the current switch port
2. Plug into a different port on the same switch
3. If link lights appear on the new port, the original port has failed
4. On a managed switch, mark the bad port as "shutdown" to prevent accidental use:

# Cisco IOS
interface FastEthernet0/1
 shutdown
 description "FAILED PORT - DO NOT USE"

Solution C: Bring up the interface manually

# Linux — the interface may be administratively down
sudo ip link set eth0 up

# Verify
ip link show eth0
# Should show: state UP LOWER_UP

# Persist across reboots (Debian/Ubuntu /etc/network/interfaces):
auto eth0
iface eth0 inet dhcp

Solution D: Force speed/duplex to resolve auto-negotiation failure

# Linux — force 100Mbps full duplex if auto-negotiation is failing
sudo ethtool -s eth0 speed 100 duplex full autoneg off

# Set the matching speed on the switch port (Cisco IOS):
interface GigabitEthernet0/1
 speed 100
 duplex full
 no shutdown

Solution E: Update or reinstall NIC drivers

# Linux — check if the driver is loaded
lspci -k | grep -A 3 "Ethernet"
# Look for "Kernel driver in use:" line

# Reload the driver
sudo modprobe -r e1000e   # replace e1000e with your driver name
sudo modprobe e1000e

# Windows — Device Manager > Network Adapters > right-click > Update Driver

• Use quality Cat5e or Cat6 cables with metal-shielded RJ45 connectors in environments with physical stress (server rooms, under desks)
• Label all cables with their source and destination to simplify future troubleshooting and replacements
• For critical infrastructure, use switches with port status monitoring and configure SNMP alerts when link state changes
• Inspect cables annually in high-traffic areas where they may be repeatedly bent, crushed by furniture, or stepped on
• Maintain a stock of tested spare cables and a cheap cable tester in your office or server room