Reviewed by Router Setup Editorial Team Last reviewed:

This symptom usually means the client joined the physical network but did not complete DHCP, or the network rejected the client before address assignment.

First checks

  1. Forget and rejoin the Wi‑Fi network or reconnect the Ethernet cable.
  2. Check whether other clients receive addresses from the same router.
  3. Inspect the router's DHCP service, address pool and client limit.

How to interpret the result

An address beginning 169.254 on many operating systems indicates that DHCP failed and the client assigned itself a fallback address. If every device is affected, restart the router and inspect DHCP. If only one device fails, reset that client's network settings or test a manual address only for diagnosis.

What this symptom usually does not prove

Do not permanently assign a random static IP without confirming the subnet, gateway and unused-address range.

Escalate with useful evidence

Record which devices are affected, whether Ethernet and Wi‑Fi behave differently, the router or gateway status, and the exact time of the fault. This evidence helps distinguish a local client issue, radio problem, routing policy, upstream service fault or failing hardware.

Before a factory reset

Restart the relevant device first and save any ISP, Wi‑Fi, reservation, port-forwarding or mesh information needed to rebuild the network. A factory reset is a configuration-recovery action, not a universal diagnostic test.

Related troubleshooting

Safety: Do not share router passwords or remote-control codes to diagnose this symptom.