When your device says it has "failed to obtain IP address," the Wi-Fi itself is often not broken. More often, the router or hotspot failed to assign your device a usable address. These issues usually involve DHCP assignment, local network conflicts, DNS, or router settings. Follow the right order and you can usually isolate the cause in a few minutes.［1］［2］

If the terms are new to you, think of an IP address as your device's house number on the network. Without that number, you may appear connected to Wi-Fi while nothing actually loads. For the basics, start with What is a VPN? A complete beginner's guide.

Key Takeaways

"Failed to obtain IP address" means address assignment failed: your device did not receive a usable address from the DHCP server.［1］

Diagnose the scope before changing settings: check whether one device is affected or the whole network is affected.

The best fix order is predictable: reconnect Wi-Fi, restart the device and router, renew the IP lease, then check DHCP and router settings.

Public Wi-Fi, school networks, and older routers trigger this often because address pools, captive portals, and compatibility issues are common.

Verify after the fix: run a VPN and network connection test to confirm that IP and DNS behavior is back to normal.

What does "failed to obtain IP address" mean?

After you connect to Wi-Fi, your device normally asks the router for an address. The router's DHCP service then assigns a local IP such as 192.168.1.x.［1］ If the request, offer, or confirmation step fails, the system may show "failed to obtain IP address," "IP configuration failure," or "Wi-Fi doesn't have a valid IP configuration."［1］［2］

That is different from not connecting to Wi-Fi at all. You may see the wireless network and enter the correct password, yet still have no usable address, so the status sits at "connected, no internet."

Why do IP configuration failures happen?

The common causes fall into a few buckets:

Cause	Typical sign	Common scenario
DHCP is not working	The device keeps obtaining an address, then fails	Old routers, public Wi-Fi, school networks
Address pool exhaustion or conflict	Only some devices can get online	Too many home devices, guest networks
Local cache or network configuration issue	Only one device fails	Phones, Windows, and macOS can all hit this
Leftover DNS or proxy settings	You get an address but websites still fail	Frequent network switching, proxy or security tools
Router settings problem	Multiple devices fail at once	DHCP disabled, MAC filtering, outdated firmware

The context matters. Home routers more often fail because of DHCP or firmware issues. Public Wi-Fi often fails because the sign-in page never appeared. School and office networks may add device limits, MAC binding, or access policies.

If the same issue comes with DNS errors, apps spinning, or pages that will not resolve, also use How to fix DNS server not responding errors.

Diagnose for 3 minutes before you fix it

Do not start by entering a static IP. First, narrow down the scope.

Check whether it is one device or the whole network

One device fails: suspect local cache, drivers, network settings, or system compatibility.
Multiple devices fail on the same Wi-Fi: suspect the router, hotspot, or DHCP service.
Only one network fails, but a mobile hotspot works: your device is probably fine; the original network is misconfigured.

Check whether Wi-Fi is connected but not authenticated

Public Wi-Fi in hotels, malls, airports, and cafes often requires a captive portal. You may appear connected to Wi-Fi, but if the sign-in page never opens, the device can remain stuck while obtaining an address or stay in limited connectivity.

Check for old settings

If you recently changed DNS, entered a static IP, installed a proxy, switched hotspots, or upgraded the system, old settings may still be active. Many sudden IP assignment failures are old configuration choices failing on a new network.

7 practical fixes, in the right order

These steps are ordered by success rate and risk. You usually do not need all of them; step 4 or 5 often solves it.

1. Disconnect and reconnect Wi-Fi, or forget the network

Turn Wi-Fi off and on, then reconnect. If that fails, choose "Forget this network" and enter the password again.

This clears the old association and starts a fresh address request. It is especially useful on public Wi-Fi, mobile hotspots, and networks where the router password recently changed.

2. Restart your phone, computer, and router

Restarting both the device and the router works better than restarting only one side. The router rebroadcasts the network, and the device starts a new DHCP request.［2］

For a home network:

Turn off Wi-Fi on the phone or computer.
Unplug the router for 30 seconds.
Wait until the router is fully online, then reconnect.

3. Check signal strength, device count, airplane mode, and time settings

This sounds basic, but it solves a lot.

Weak signal can interrupt the DHCP handshake.
Too many connected devices can exhaust the address pool.
Frequent airplane mode toggles, wrong system time, or recent hotspot switching can affect reassignment.

On school, office, or mall Wi-Fi, also check whether there is a device limit, web sign-in page, or MAC binding.

4. Release and renew the IP address, or renew the DHCP lease

If the first 3 steps fail, move to system-level troubleshooting.

On Windows, open Command Prompt and run ipconfig /release followed by ipconfig /renew. Microsoft also includes these actions in network troubleshooting guidance.［2］

On macOS, iPhone, or iPad, renew the lease from the network settings. Apple also recommends rejoining the network or checking wireless settings when Wi-Fi behaves incorrectly.［3］

If you suspect VPN or DNS problems are involved, run How to test whether your VPN connection is working after the fix.

5. Use a static IP temporarily for testing

If DHCP assignment seems broken, temporarily enter a static IP in the same subnet to test the path.

This is useful when:

the router appears healthy, but the device never gets an address;
other devices on the same network work, but this one repeatedly fails.

Use static IP as a test, not the default long-term fix. A wrong gateway, subnet mask, or DNS value can make the problem harder. If you are unsure, skip this step.

6. Check router DHCP, encryption, MAC filtering, and firmware

If several devices fail together, inspect the router.

Look for:

DHCP service disabled;
a DHCP address pool that is too small;
MAC filtering or guest network restrictions;
outdated or incompatible Wi-Fi encryption;
firmware that has not been updated for years.

Older routers can show Wi-Fi normally but fail IP assignment when mixed modes, band steering, or guest network settings are misconfigured.

7. Update drivers or the system, then cross-test with Ethernet or another device

The final step is ruling out compatibility problems.

Windows users can update the wireless adapter driver.
macOS, iPhone, and Android users can check system updates.
Desktops and laptops can test Ethernet.
You can also connect another phone or computer to the same network.

If another device works, the current device is more likely at fault. If every device fails, the router, hotspot, or network environment is the likely cause.

How to handle it on Windows, Mac, phones, and game consoles

Different platforms have different troubleshooting entry points.

Windows

On Windows, forget the network, disable and re-enable the adapter, renew the IP lease, and update the wireless driver.［2］ If you see "Wi-Fi doesn't have a valid IP configuration," prioritize step 4 and step 7.

Mac

On Mac, start with Wi-Fi settings and TCP/IP lease renewal. If you previously changed DNS or IPv4 settings, check for leftovers.［3］

Phones

Phones hit this most often on public Wi-Fi, hotel networks, metro and mall hotspots, and mobile tethering. Forgetting the network, toggling airplane mode, and reopening the captive portal often work better than advanced settings.

Game consoles and TVs

These devices have fewer settings and weaker diagnostics. If they fail to obtain an IP address, test the same network with a phone or computer first, then decide whether router settings need changes. Do not start by manually entering many parameters on the console.

How can you prevent the error next time?

Fix the common triggers before they repeat.

Keep router firmware updated, especially on devices older than three years.
Do not mix static IP and automatic assignment unless you understand the network.
On public Wi-Fi, finish the sign-in page before opening regular apps.
If your home has many devices, expand the DHCP address pool.
On devices that switch networks often, keep DNS and network policies stable, and avoid low-quality proxy tools.

If your real goal is safer and steadier public Wi-Fi, also read Should you use a VPN on public Wi-Fi?.

Summary

"Failed to obtain IP address" usually means DHCP assignment or local configuration failed; it does not mean Wi-Fi hardware is broken.
The safest order is to identify the scope, reconnect, restart, renew the IP lease, then check router and system compatibility.
Home routers, public Wi-Fi, school networks, and mobile hotspots are the most common triggers.
After fixing it, verify websites, apps, IP, and DNS, instead of trusting the word "connected."

FAQ

Is "failed to obtain IP address" the same as "DNS server not responding"?

No. The first usually happens before the device receives a local network address. The second usually happens after the device is online but domain resolution fails. They can appear together, but they are different steps.

Only my phone cannot connect, while other devices work. What does that mean?

It usually means the phone is more likely the problem than the router. Try forgetting the network, restarting the phone, toggling airplane mode, and checking whether static IP or private DNS was set manually.

Can a static IP permanently solve it?

Not always. Static IP is better as a DHCP test or for a few fixed networks. For most home users, automatic assignment is still easier and safer.

Why is public Wi-Fi more likely to cause IP configuration failure?

Public Wi-Fi has many users, frequent device churn, captive portals, time limits, device limits, and tight address pools. Seeing the signal does not mean the address was successfully assigned.

Can a VPN directly fix "failed to obtain IP address"?

No. If your device has not received a local network address, the VPN usually cannot start yet. A VPN helps after the network is restored by improving privacy, reducing DNS hijacking risk, and smoothing network switching.

Should I factory reset the router?

Only if several devices fail, normal fixes do not work, and you know how to reconfigure the network. For most people, checking DHCP, firmware, and MAC filtering is enough.

Disclaimer

This article is for general network troubleshooting information only and does not constitute professional operations, enterprise IT, or legal advice. When changing static IP, router admin, or system network settings, make sure you understand the parameters first.

AethoVPN cannot perform the account, device, or offline checks in “Failed to obtain IP address”.

Sources

RFC Editor - Dynamic Host Configuration Protocol (RFC 2131) — https://www.rfc-editor.org/rfc/rfc2131
Microsoft Support - Fix network connection issues in Windows — https://support.microsoft.com/en-us/windows/fix-network-connection-issues-in-windows-10-166a28c4-14c1-bdb1-473c-09c1571455d8
Apple Support - If your Mac doesn't connect to the Internet over Wi‑Fi — https://support.apple.com/en-us/102766

Sources checked 8 May 2026.

Related Articles:

Failed to obtain IP address