Updated October 8, 2026: corrected the macOS DHCP instructions and added checks to distinguish address assignment from DNS or ISP problems.
What a self-assigned 169.254 address means
On a home network configured to use DHCP, an unexpected 169.254.x.x IPv4 address usually means the device did not obtain a usable DHCP lease. Windows calls its fallback mechanism APIPA. macOS may display “Self-Assigned IP.”
These IPv4 link-local addresses can support communication on the same link, but routers do not forward them for normal internet access. They do not, by themselves, prove an IP conflict or mean the device has no possible connectivity: an independently working IPv6 connection may still be present.
The IETF specification for IPv4 link-local addressing explains the scope of this range. If you already have an expected address and gateway, use the connected-but-no-internet checks instead of assuming DHCP failed.
1. Check the active adapter
On Windows:
ipconfig /allRead the IPv4 address, subnet mask, default gateway, and DHCP Enabled field under the connected Wi-Fi or Ethernet adapter. Ignore disconnected and unused virtual adapters. On Mac, open System Settings → Network → your active service → Details → TCP/IP.
Check another device on the same network. If multiple devices cannot obtain leases, investigate the router's DHCP service or network path. If only one fails, start with that device's settings and connection.
2. Renew the DHCP lease
This can briefly interrupt connectivity. Perform it locally, not through the connection supporting a remote session.
Windows
For an adapter configured to obtain its address automatically:
ipconfig /release
ipconfig /renewMicrosoft documents these options in its ipconfig reference. Check the active adapter again afterward.
Mac
Open System Settings → Network → active service → Details → TCP/IP → Renew DHCP Lease. The option is available when the service uses DHCP. Older macOS releases place it in Network → Advanced → TCP/IP.
Use the macOS control rather than Linux dhclient commands, which are not supplied as standard macOS DHCP tools. See Apple's TCP/IP settings documentation.
Linux
Use the network manager already controlling the interface. On a NetworkManager desktop, disconnect and reconnect the affected connection in the network settings. Other systems may use systemd-networkd or another manager; follow that manager's renewal procedure rather than starting a second DHCP client.
Verify the result
Confirm an address valid for your actual network, the correct mask, and the expected gateway. Then test the gateway and ordinary internet access. Private addresses can begin with 10, 192.168, or 172.16 through 172.31; do not require one particular prefix.
3. Reconnect the affected device
Disconnect and rejoin Wi-Fi, or check the Ethernet cable and link. If necessary, forget the saved Wi-Fi network and join again with the correct password. On current Macs, the connected network's Wi-Fi Details includes Forget This Network. Mobile menus vary by version.
If the device's address is manually configured, check whether that was intentional. Restore automatic DHCP only where the network is meant to assign addresses automatically.
4. Check the router when multiple devices are affected
Use a working device to open the router's admin interface. Check that the intended LAN has DHCP enabled and enough available leases. Confirm the pool matches that LAN's subnet and does not conflict with manual addresses or reservations.
Do not enable a second DHCP server on a mesh node or access point just because it has a DHCP option. The correct server depends on the network design.
A controlled router restart can help if its DHCP service is stuck; it interrupts everyone using the connection. If DHCP still fails, review firmware, lease capacity, and the link between access point and router. On a work network, give these observations to the administrator.
5. Check filtering and private Wi-Fi addresses
If the router uses a MAC allowlist, compare it with the address the device currently uses for that Wi-Fi network. A private address can differ from the hardware label. Our unknown-device guide explains how to match it.
Review security software or network policies that might block DHCP. Check logs and targeted rules rather than disabling the whole firewall.
Should you set a static IP as a workaround?
Only if you know the network's subnet, gateway, DNS settings, and a verified unused address that will not overlap the dynamic DHCP pool. An arbitrary 192.168.1.50 may be wrong for your network or already assigned to another device.
A manual address does not repair DHCP and cannot fix an ISP outage. Prefer restoring the intended DHCP service, and return the device to automatic configuration afterward if that is the network's design.
When to investigate something else
If you receive a valid lease but still cannot browse, check DNS, the default route, a captive portal, VPN policy, and the router's WAN connection using the Wi-Fi troubleshooting guide. If internet access works but local devices remain invisible, use the network scanner guide.