Networking: `arp -n` shows (incomplete) / Destination Host Unreachable — no ARP reply from the next hop
The machine asked "who has this IP?" and nobody on the local network answered.
arp -a (incomplete)192.168.1.20 dev eth0 FAILED192.168.1.20 dev eth0 INCOMPLETEARP request unansweredat <incomplete> on eth0 Meaning
ARP failing on the same subnet means the target is off, on another VLAN, has a different IP, or a switch/Wi-Fi isolation feature blocks the broadcast. Verify the IP and subnet mask, check the VLAN and port, and capture with tcpdump -i eth0 arp.
Common causes
- Target host is down or unplugged
- Wrong IP or subnet mask
- Different VLAN or Wi-Fi client isolation
- Switch dynamic ARP inspection blocking
- Firewall on the target dropping ARP/ICMP
⚡ Quick fix
- Confirm both hosts share subnet and VLAN
- Watch the request:
sudo tcpdump -ni eth0 arp - Disable client isolation or fix the VLAN
Detailed fix by platform
Linux
ip neigh show | grep -E "FAILED|INCOMPLETE"; sudo arping -I eth0 192.168.1.20
How to diagnose
- Neighbour state — FAILED/INCOMPLETE?
- Subnet/VLAN — Same?
- Target — Powered on?
🔧 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
- 4-way handshake timeout / Incorrect password Networking: wlan0: WPA: 4-way handshake failed - pre-shared key may be incorrect / WRONG_KEY
- Cannot assign requested address (EADDRNOTAVAIL) Networking: connect: Cannot assign requested address — ephemeral port range exhausted by TIME_WAIT connections
- DHCPDISCOVER: no free leases Networking: dhcpd: DHCPDISCOVER from aa:bb:cc:dd:ee:ff via eth0: network 192.168.1.0/24: no free leases
Most viewed in Networking
- 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
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
- dig: status: SERVFAIL (DNSSEC validation failed) Networking: dig: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL — resolver failed to answer (DNSSEC validation or upstream failure)
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