Windows s,attributes an APIPA address when it fails to get a DHCP configuration.
Probable causes
Only one station in 169.254 can have a local card, driver or network stack problem while the DHCP is running. Conversely, several affected customers on the same VLAN are pointing to the link, relay or server. Avoid, immediately assigning a static IP: this masks the defect of the DHCP I’m not gonna solve it…
Verifications.
Check first the physical or Wi-Fi connection and run…. ipconfig /all To confirm the APIPA address, the card used and the no DHCP lease. Test a second post on the same port or SSID, then check the VLAN, DHCP relay/IP helper and the available range on the server side. A DHCP capture can show if the DHCP exits and if a Offer returns….
Solutions…
After correction, start…ipconfig /release then…. ipconfig /renew or reconnect the interface properly, then check the address, mask, gateway and DNS received.Please ensure that the lease appears on the server side and that a restart or subsequent reconnection still gets a valid address. The result must be reproducible without manual configuration…
FAQ — PC gets an address 169.254.x.x….
169.254 does it mean that the network card works?….
It is at least locally active, but this does not prove that the path to the DHCP server is operational….
Why is one post affected?….
The problem can be local: driver, interface, port, network authentication or battery-tit/IP….
What if a whole VLAN is hit?….
DHCP relay, ACLs, DHCP range, server availability and network path between clients and server….