Wi-Fi Has No IP Address: What It Means and How to Fix It
Appears on: Windows, macOS, Android, iOS. "Wi-Fi has no IP address" — or seeing a 169.254.x.x address — means DHCP failed: your device associated with the Wi-Fi access point at the radio level but the router never assigned it an IP address. Without an IP, no internet traffic can flow.
What "no IP address" actually means
When you connect to Wi-Fi, your device sends a DHCP Discover broadcast asking the router to assign it an IP address. The router's DHCP server responds with an IP, subnet mask, gateway, and DNS server. If no DHCP response arrives, Windows self-assigns a 169.254.x.x APIPA address — a placeholder that has no route to the internet. You'll show as "connected" to Wi-Fi but no browser, app, or ping to the internet will work. macOS shows "No IP address" in the Wi-Fi details; Android may show "Obtaining IP address…" indefinitely.
Most likely causes (ranked)
- Stale or conflicting DHCP lease — the router thinks the IP is already assigned
- Router DHCP pool exhausted — too many devices, no free addresses left
- Windows DHCP Client service stopped or crashed
- IP address conflict — another device on the network has the same IP
- Router firmware bug or corrupted DHCP state — fixed by restarting the router
How to fix Wi-Fi has no IP address
Step 1: Release and renew the IP address
Windows (Command Prompt as admin):
ipconfig /release
ipconfig /renewmacOS (Terminal — find your interface with ifconfig, usually en0 for Wi-Fi):
sudo ipconfig set en0 DHCPThis forces a fresh DHCP negotiation and typically resolves stale lease issues immediately.
Step 2: Forget and reconnect to the Wi-Fi network
Windows: Settings → Network & internet → Wi-Fi → Manage known networks → select your network → Forget. Reconnect by selecting the network and entering the password.
macOS: System Settings → Wi-Fi → click the network name → Forget This Network. Reconnect manually.
Step 3: Restart the DHCP Client service (Windows)
Press Win+R → type services.msc → find DHCP Client → right-click → Restart. If the service shows "Stopped", right-click → Start. A stopped DHCP Client prevents all IP address negotiation regardless of network state.
Step 4: Restart the router
Unplug the router's power for 30 seconds, then plug back in and wait 2 minutes. If the router's DHCP state was corrupted or its lease table was full, a restart clears it. All connected devices will renegotiate DHCP after the router restarts.
Step 5: Check the DHCP pool in your router admin page
Log into your router (usually 192.168.1.1 or 192.168.0.1) → DHCP settings. Check the lease pool range and the number of active leases. If the pool is exhausted — all addresses assigned — either increase the pool range (e.g., from .100–.150 to .100–.200) or reduce the lease time to free up stale addresses faster.
Frequently Asked Questions
What does a 169.254.x.x address mean?
169.254.x.x is an APIPA address — Windows self-assigns this when DHCP fails and no static IP is configured. It means DHCP discover broadcasts got no response from the router. APIPA addresses are non-routable and cannot reach the internet.
Why does this happen to one device but not others on the same network?
If other devices connect fine, the issue is device-specific: a stale DHCP lease, corrupted adapter state, or stopped DHCP Client service. Run ipconfig /release /renew, forget and reconnect, and restart the DHCP Client service. If the router's DHCP pool is exhausted, all new connection attempts will fail — check the router admin for active lease count.
Related Guides
Default Gateway Not Available
When you have an IP but the path to the router is broken.
Wi-Fi Connected But No Internet
Full playbook for when Wi-Fi shows connected but nothing loads.
Flush DNS Cache
Clear stale DNS entries after fixing IP address issues.
This Site Can't Be Reached
Browser errors that result from having no valid IP address.