Solution:
Root Cause: DHCP discovery failed and Windows assigned an APIPA address When a DHCPDISCOVER broadcast receives no reply, Windows self-assigns an address in 169.254.0.0/16 (APIPA). That range is not routable and has no gateway, so traffic to 192.168.1.1 never reaches the router. The usual causes are a bad cable or switch port, an exhausted router DHCP pool, a hung DHCP service on the router, or a wireless client that associated without completing a lease.
Diagnostic Verification: Run ipconfig /all and look for 'Autoconfiguration IPv4 Address' with a 169.254.x.x value and no Default Gateway. Open Event Viewer > Applications and Services Logs > Microsoft > Windows > Dhcp-Client > Admin and look for failed lease events. Run ping 192.168.1.1. Request timed out or General failure confirms no Layer 3 path. Step-by-Step Fix: 1 Verify the physical link:
Try a different Ethernet cable and a different LAN port on the router (not the WAN or Internet port). Confirm the link light is on at both ends. 2 Renew the DHCP lease from an elevated terminal:
Copy
powershell
ipconfig /release
ipconfig /renew
3 Assign a temporary static address to reach the admin page:
Replace Ethernet with your adapter name if it differs.
Copy
powershell
netsh interface ip set address name='Ethernet' static 192.168.1.50 255.255.255.0 192.168.1.1
4 Open http://192.168.1.1, then restore DHCP and fix the lease pool:
Increase the DHCP pool size or reduce the lease time in the router's LAN settings. Return the PC to automatic addressing with the command below.
Copy
powershell
netsh interface ip set address name='Ethernet' source=dhcp
5 Power cycle the router if DHCP still fails:
Unplug it for 30 seconds, plug it back in, and wait 2 minutes before retesting. Prevention & Long-Term Monitoring: Keep the DHCP pool larger than the number of devices you own, including phones and smart-home devices. Use DHCP reservations for printers, NAS units and servers instead of unmanaged static addresses.