Networks guide
Devices Not Getting an IP Address (169.254.x.x): DHCP Troubleshooting for Offices
A computer with an address beginning 169.254 has asked the network for configuration and received no answer. Windows assigns itself that address as a fallback, and nothing beyond the local segment will work. The question is why the DHCP server didn't respond.
Step-by-step
Confirm the symptom
On an affected Windows computer, run
ipconfig /all. An IPv4 address starting 169.254 confirms DHCP failure. Runipconfig /releasefollowed byipconfig /renewto retry; note any error returned.Check whether the scope is full
Open the DHCP leases page on your router or firewall, or the scope statistics in the Windows DHCP console. If every address is in use, new devices are refused. Expanding the scope, shortening lease times for guest networks, and removing stale reservations all free capacity.
Confirm the DHCP service is running
If the scope has free addresses but nobody receives one, check the DHCP service itself: the router's status, or the DHCP Server service and event logs on a Windows server. A server that has recently been rebooted, updated or moved is the usual suspect.
Look for a rogue DHCP server
A consumer router or access point plugged into the office network with its own DHCP enabled will hand out the wrong addresses. Affected devices will show an unexpected address range and gateway. Find the device by its MAC address in the switch tables and disable its DHCP, or remove it. Managed switches can block this with DHCP snooping.
Check VLAN relay
Where the office uses separate VLANs for staff, guests, phones or printers, each VLAN needs either its own DHCP scope or a DHCP relay (IP helper) configured on the router or core switch. A new VLAN without one will leave every device on it at 169.254.
Prevention
Size scopes for growth, give printers and network equipment reservations, keep guest devices on a separate network with short leases, and monitor scope utilization so you're alerted before it runs out.