Networking: Network cable unplugged / `ip link` shows NO-CARRIER state DOWN / Ethernet: Network cable unplugged
The network card sees no electrical link, so nothing above it (IP, DNS, browser) can work.
Network cable unpluggedEthernet: Network cable unpluggedNO-CARRIER state DOWNeth0: link is not readyLink detected: no Meaning
This is layer 1: the NIC reports no carrier. Reseat or replace the cable, try another switch port, check the link LEDs and the wall jack. In Linux NO-CARRIER with state DOWN in ip link means no link; on VMs make sure the virtual cable is connected in the hypervisor.
Common causes
- Loose, damaged or too-long cable
- Dead switch port or wall jack
- Switch port administratively shut down
- NIC disabled or driver problem
- Virtual NIC not connected in the VM settings
⚡ Quick fix
- Reseat both ends or swap the cable
- Try a different switch port or device
- Run
ip link show/ethtool eth0and look forLink detected: yes
Detailed fix by platform
Linux
ip -br link show && sudo ethtool eth0 | grep -E "Speed|Duplex|Link detected"
How to diagnose
- Link LED — On?
- ethtool — Link detected?
- Other cable/port — Works?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- arp -a shows (incomplete) Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- Duplex mismatch: late collisions / CRC errors Networking: Duplex mismatch — late collisions, runts and CRC errors on the switch port
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026