APIPA / 169.254.x.x Addresses

Problem

A device has self-assigned an IP address in the 169.254.0.0/16 range instead of getting one from DHCP.

Symptoms

• No internet or local network access
• ipconfig shows an address starting with 169.254
• Other devices on the same network work fine

Possible Causes

• DHCP server unreachable or down
• DHCP scope exhausted (no addresses left to hand out)
• Faulty cable or switch port preventing the DHCP request from completing
• Rogue or misconfigured second DHCP server on the network

Diagnostic Steps

1. Run ipconfig /all to confirm the exact 169.254.x.x address
2. Check whether other devices on the same segment are also affected
3. Check the DHCP server/router for its current lease count and scope size

Commands & Tools

Step-by-Step Solution

1. Run ipconfig /release then ipconfig /renew to request a fresh lease
2. Restart the network adapter, or the device itself, if renew fails
3. Confirm the DHCP server/router is powered on and its service is running
4. If the scope is exhausted, expand the DHCP range or shorten lease duration
5. If multiple devices are affected, search for and disable any unauthorized second DHCP server on the network

Verification

ipconfig shows a normal address within the expected subnet, and the device can reach the gateway and internet.

Common Mistakes

• Assuming it's a DNS problem when the address itself is the real issue
• Not checking whether the problem is isolated to one device or the whole segment
• Overlooking a rogue DHCP server as the cause when several unrelated devices fail at once

Escalation Criteria

Prevention

Monitor DHCP scope utilization, document static reservations clearly, and lock down switch ports to prevent unauthorized devices from serving DHCP.

Related Articles