A device that shows “no internet” with a self-assigned 169.254.x.x address is a DHCP failure, not a general connectivity problem — the exact address a client falls back to tells you a lot before you even open the router’s configuration.
Common Symptoms
- Client devices show a 169.254.x.x “APIPA” address
- Client devices can’t get any IP address at all
- Only some devices fail to get an address, not all
Possible Causes
- The DHCP server is disabled or bound to the wrong interface
- The address pool is exhausted (all leases in use)
- A VLAN or bridge misconfiguration preventing DHCP broadcasts from reaching the server
- A duplicate/rogue DHCP server on the same network
Before You Begin
Confirm which interface/VLAN the affected devices are physically connected to — DHCP problems are very often scoped to one interface rather than the whole network.
Method 1 — Confirm the DHCP server is running
Check DHCP server status
IP → DHCP Server — confirm the server is enabled and bound to the correct interface for the affected devices.
Method 2 — Check the address pool
Review the pool range and leases
IP → Pool — check the range isn’t exhausted. IP → DHCP Server → Leases shows currently issued addresses.
Method 3 — Check for a rogue DHCP server
Look for unexpected lease ranges
If some devices get addresses from an unexpected subnet, another device on the network (a second router, an access point in router mode) may be handing out conflicting DHCP leases.
Never plug a second consumer router into the LAN with its own DHCP server still enabled — this is one of the most common causes of intermittent, hard-to-diagnose IP conflicts in small offices.
Frequently Asked Questions
What does a 169.254.x.x address mean?
That’s an APIPA (Automatic Private IP Addressing) address — the device assigns it to itself when it can’t reach any DHCP server at all, confirming the problem is DHCP, not routing or DNS.
Conclusion
Checking that the DHCP server is enabled on the correct interface, and that the address pool isn’t exhausted, resolves the majority of “no IP address” reports.
Related Articles
