What this page covers
Separate physical link, DHCP reachability and manual/static configuration before changing the router.
Step-by-step workflow
- Confirm the active adapter is the one connected to the intended network.
- Check link status and cable or Wi-Fi association.
- Renew the lease using the platform’s documented command.
- Compare with another authorised client on the same segment.
Decision table
| Check | What it tells you | Safe next action |
|---|---|---|
| One client has 169.254 | Device-side issue is more likely | Recheck adapter and profile |
| All clients have it | DHCP or network path is likely | Check router LAN/DHCP service |
| Static configuration present | APIPA may be a fallback or stale profile | Restore the intended documented mode |
Limits and verification
Do not infer a router address from an APIPA result. The correct next step is to identify the network path and DHCP source.
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
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.