What this page covers
Use the client’s current address, DHCP-server field and a controlled wired/Wi-Fi comparison to isolate the failing segment.
Step-by-step workflow
- Check whether one or every device is affected.
- Inspect IP, mask, gateway and DHCP-server fields on the affected device.
- Swap only one variable: cable, port, band or authorised access point.
- Restart the DHCP service or router only after recording the current topology.
Decision table
| Check | What it tells you | Safe next action |
|---|---|---|
| 169.254.x.x | The client did not receive a normal lease | Check link, VLAN and DHCP scope |
| One device only | Client adapter or profile may be involved | Forget/rejoin or renew on that device |
| All clients | Router, uplink or provider handoff may be involved | Check router status before reset |
Limits and verification
A DHCP timeout does not prove that the router is dead. A guest network, VLAN, bridge mode, exhausted pool or second router can produce a similar symptom.
Official sources
- IETF RFC 2131 — Dynamic Host Configuration Protocol (DHCP message and lease concepts)
- Microsoft — Essential network settings and tasks (Windows network fields and commands)
Related Router Portal guides
Find the current gateway · Router login troubleshooting · Subnet calculator
Keep in mind: Firmware, operating-system menus, ISP policies and regional radio rules can change. Confirm the current official source and exact device before applying a setting.
Our networking steps are lab-tested against standard RFC 1918 private networking protocols across Windows 11 (24H2), macOS Sequoia (15.1), iOS 18, and Android 15. We verify physical device labels and firmware release documentation before publishing gateway instructions. Router Portal is strictly read-only and never requests, intercepts, or logs router passwords.