You try to connect to your WiFi network, and instead of a quick connection, your phone just sits there displaying “Obtaining IP Address.” It spins and spins, sometimes for minutes, before failing or repeating endlessly. Learning how to fix the obtaining IP address loop on a Wi-Fi network can save you from a lot of frustration.
This problem hits Android users most often, but it also affects iPhones, Windows laptops, macOS devices, and gaming consoles like the PS5. The root cause is nearly always a breakdown in the communication between your device and the router’s DHCP server.
In this guide, our team walks you through every fix that works, starting with quick 30-second solutions and moving into advanced router-level adjustments. We also cover device-specific steps for Android, iOS, Windows, macOS, and gaming consoles.
Table of Contents
What Is the Obtaining IP Address Loop?
The “Obtaining IP Address” loop happens when your device sends a request to the router asking for an IP address but never receives a valid response. Without that IP address, your device cannot send or receive data on the network. The connection process stalls, and the status message stays stuck on “Obtaining IP Address.”
This request happens through a protocol called DHCP (Dynamic Host Configuration Protocol). When you tap your WiFi network name, your device sends a DHCP Discover message to the router. The router should respond with a DHCP Offer containing an available IP address. Your device confirms with a DHCP Request, and the router finalizes with a DHCP Acknowledgment.
If any step in that four-part handshake fails, times out, or gets blocked, the loop begins. Your device retries the request, the router either does not respond or responds incorrectly, and the cycle repeats indefinitely.
The most common symptom is the status text “Obtaining IP Address” that never changes. Sometimes it eventually shows “IP Configuration Failure,” “Failed to Obtain IP Address,” or “Bad Connection.” In other cases, the status just bounces between “Connecting” and “Obtaining IP Address” without ever reaching “Connected.”
Why Does My WiFi Get Stuck on Obtaining IP Address?
Understanding the cause helps you pick the right fix. Multiple things can break the DHCP handshake, and the solution depends on which link in the chain is failing.
Router-side causes: The router’s DHCP server may have run out of available IP addresses in its pool. This happens when too many devices have connected and old leases have not expired. The DHCP service on the router could also be glitching, frozen, or misconfigured. In some cases, MAC address filtering is blocking your device from receiving an address.
Device-side causes: Your phone or computer may have a corrupted DHCP cache that sends malformed requests. A stale network profile can also cause the device to send incorrect connection parameters. After system updates, especially Android updates, the WiFi driver or DHCP client can behave differently and fail to complete the handshake.
Signal and interference issues: This is an overlooked cause that many guides skip entirely. If your WiFi signal is weak or experiencing interference, the DHCP packets can get lost in transit. The router sends the IP address offer, but your device never receives it clearly enough to process. You will see the “Obtaining IP Address” loop even though the problem is physical signal quality, not an IP configuration issue.
Old router and newer Android incompatibility: Many users on Reddit and XDA Forums report that newer Android versions have stricter DHCP timeout behavior. Android 12 and later enforce shorter timeout windows and reject DHCP responses that older routers send in a non-standard format. The router works fine with older phones and laptops, but newer Android devices reject the handshake because the router’s response does not meet modern RFC standards.
Network configuration mismatches: Public WiFi, hotel networks, and office networks often have captive portals, splash pages, or custom DHCP configurations. These can interfere with the standard DHCP handshake and trigger the loop on devices expecting a normal home network connection.
Quick Fixes to Try First
Before diving into anything complicated, try these quick fixes. They resolve the problem in the majority of cases and take less than a minute each.
1. Toggle WiFi Off and On
Turn off your WiFi, wait ten seconds, and turn it back on. This forces your device to start a fresh DHCP request instead of retrying a failed one. It clears the current connection state and gives the router a clean slate to respond to.
2. Toggle Airplane Mode
Enable airplane mode for ten seconds, then disable it. This resets all radio connections including WiFi, cellular, and Bluetooth. Many users on Reddit report that this single step fixes the obtaining IP address loop on Android phones more often than any other quick fix.
Airplane mode works because it completely shuts down the network stack and restarts it cleanly. A simple WiFi toggle sometimes leaves background processes running that interfere with the new connection attempt.
3. Forget and Reconnect to the Network
Go to your WiFi settings, find the network giving you trouble, tap it, and select “Forget Network” or “Forget.” Then reconnect by entering the password again.
This deletes the stored network profile, including any cached DHCP data, saved IP configuration, and authentication tokens. When you reconnect, your device starts the entire DHCP handshake from scratch. This is particularly effective if the problem started after a router reboot or a network settings change.
4. Restart Your Device
A full restart clears the system memory, restarts the WiFi driver, and resets the DHCP client service. If you have an Android phone, power it off completely, wait 15 seconds, and power it back on. On iPhones and iPads, do a full shutdown rather than just a sleep-wake cycle.
5. Restart Your Router
Unplug your router from power, wait 30 seconds, and plug it back in. Wait another 60 seconds for it to fully boot up before trying to connect again. This clears the DHCP lease table, restarts the DHCP server service, and frees up any stuck IP assignments.
If these five quick fixes do not resolve the issue, move on to the device-specific troubleshooting steps below.
Device-Specific Troubleshooting
Different operating systems handle DHCP differently. Here is how to fix the obtaining IP address loop on each major device type.
Fixing the Loop on Android (Including Android 12 and Later)
Android is the platform where this problem appears most frequently. The steps below cover both older versions and the behavior changes introduced in Android 12 and later.
Step 1: Reset network settings. Go to Settings, then System, then Reset options, and tap “Reset Wi-Fi and Bluetooth settings” or “Reset network settings.” This clears all saved WiFi networks, Bluetooth pairings, and cellular settings. You will need to re-enter your WiFi passwords afterward, but it wipes out any corrupted DHCP data that could be causing the loop.
Step 2: Try a static IP. Go to your WiFi settings, tap the network name (or the gear icon next to it), tap Advanced, and change “IP Settings” from DHCP to Static. Enter an IP address that is within your router’s subnet but outside its DHCP pool. For most home routers, something like 192.168.1.200 works. Set the gateway to your router’s IP (usually 192.168.1.1) and use 8.8.8.8 for DNS.
Step 3: Check for Android 12+ specific behavior. Android 12 introduced a redesigned network stack called “NetworkMainline” that handles DHCP differently. If your phone updated to Android 12 or later recently and the obtaining IP address loop started right after, the new network stack may be rejecting your router’s DHCP responses. Updating your router firmware or assigning a static IP on the device side are the most reliable fixes.
Step 4: Clear the DHCP cache (root required). If your device is rooted, you can delete the DHCP cache files directly. Use a file explorer with root access and navigate to /data/misc/dhcp/. Delete all files in that directory, then reboot your phone. This clears stale DHCP state data that survives normal network resets.
Fixing the Loop on iPhone and iPad (iOS)
Apple devices encounter this problem less frequently than Android, but it does happen. Here is how to handle it on iOS.
Step 1: Forget the network. Go to Settings, tap WiFi, tap the info icon next to the network, and tap “Forget This Network.” Reconnect by entering the password.
Step 2: Reset network settings. Go to Settings, then General, then Transfer or Reset iPhone, then Reset, and tap “Reset Network Settings.” This wipes all saved WiFi networks and passwords but does not delete your apps, photos, or other data.
Step 3: Configure a manual IP. Tap the info icon next to your connected WiFi network, tap “Configure IP,” and switch from Automatic to Manual. Enter an IP address in your router’s subnet range, along with the subnet mask and router address.
Step 4: Disable Private WiFi Address. iOS 14 and later uses a private MAC address for each WiFi network by default. Some older routers do not handle this well and fail the DHCP handshake. Tap the info icon next to your network and turn off “Private Wi-Fi Address” to see if it resolves the loop.
Fixing the Loop on Windows
On Windows 10 and 11, the obtaining IP address loop usually appears as “No Internet, Secured” or an “IP Configuration Failure” error.
Step 1: Release and renew the IP address. Open Command Prompt as Administrator. Type ipconfig /release and press Enter. Then type ipconfig /renew and press Enter. This forces Windows to release its current IP and request a fresh one from the router’s DHCP server.
Step 2: Flush the DNS cache. In the same Command Prompt, type ipconfig /flushdns and press Enter. This clears cached DNS data that could be interfering with network resolution.
Step 3: Reset the TCP/IP stack. Type netsh int ip reset and press Enter, then restart your computer. This rebuilds the entire TCP/IP stack from scratch, which clears any corrupted network configuration data.
Step 4: Update the wireless network adapter driver. Right-click the Start button, open Device Manager, expand “Network adapters,” right-click your WiFi adapter, and select “Update driver.” Choose the automatic search option. An outdated driver can cause DHCP handshake failures.
Fixing the Loop on macOS
Mac users can encounter this issue too, especially on public and hotel networks. Here are the steps that work.
Step 1: Renew the DHCP lease. Go to System Settings (or System Preferences), click Network, select your WiFi connection, and click “Details” or “Advanced.” Under the TCP/IP tab, click “Renew DHCP Lease.” This forces your Mac to request a new IP address from the router.
Step 2: Delete WiFi configuration files. Open Finder, press Command+Shift+G, and navigate to /Library/Preferences/SystemConfiguration/. Delete the files named com.apple.network.eapnetworkconfiguration.eapclient.xml, com.apple.wifi.message-tracer.plist, NetworkInterfaces.plist, and preferences.plist. Restart your Mac. This forces macOS to rebuild its entire network configuration from scratch.
Step 3: Create a new network location. In Network settings, use the location dropdown to create a new location. This starts fresh with default network settings instead of using your existing (potentially corrupted) configuration.
Fixing the Loop on Gaming Consoles (PS5 and Xbox)
No competitor guide covers gaming consoles, but this is a growing problem. Many PS5 and Xbox owners see “Cannot Obtain IP Address” errors when connecting to WiFi.
PS5 fix: Go to Settings, then Network, then Settings, then “Set Up Internet Connection.” Select your WiFi network and instead of using the default automatic setup, choose “Manual” for IP Address Settings. Enter a static IP (for example, 192.168.1.50), set the subnet mask to 255.255.255.0, set the default gateway to your router’s IP, and use 8.8.8.8 for the primary DNS. This bypasses the DHCP handshake entirely.
Xbox fix: Go to Settings, then General, then Network Settings, then “Advanced Settings,” then “IP Settings.” Change from Automatic to Manual. Enter the same type of static IP configuration described for the PS5. You can also try power cycling the console by holding the power button for 10 seconds to fully shut it down, waiting 30 seconds, and restarting.
Common console cause: Gaming consoles are often placed far from the router and connect over weak WiFi. The DHCP packets get lost due to signal degradation, causing the “cannot obtain IP address” error. Move the console closer to the router during setup, or use a wired Ethernet connection to eliminate WiFi as a variable.
Advanced Solutions
If the quick fixes and device-specific steps have not worked, the problem likely lives on the router side or requires deeper configuration changes.
Assign a Static IP Address
We mentioned this as a workaround in several sections above, but it deserves its own explanation because it is the single most reliable fix for the obtaining IP address loop. By assigning a static IP, you skip the DHCP handshake entirely. Your device already knows its IP address and does not need to ask the router for one.
On your device, change the IP settings from DHCP to Static. Use an IP address within your router’s subnet but outside the DHCP assignment pool. For example, if your router assigns addresses from 192.168.1.100 to 192.168.1.200, use 192.168.1.201 or higher. Set the subnet mask to 255.255.255.0, the gateway to your router’s IP address, and the DNS to 8.8.8.8 (Google DNS) or 1.1.1.1 (Cloudflare DNS).
The downside of a static IP is that you must manually configure it on each network. It is inconvenient for public WiFi and networks you visit temporarily. But for your home network, it is a permanent fix that stops the loop from ever returning.
Adjust Router DHCP Settings
Access your router’s admin panel by typing its IP address (usually 192.168.1.1 or 192.168.0.1) into a browser. Log in with your admin credentials.
Increase the DHCP address pool: Navigate to the DHCP or LAN settings section. Increase the range of available IP addresses. If the pool is small (for example, only 50 addresses), expand it to 100 or more. This ensures the router never runs out of addresses to assign.
Reduce lease time: Set the DHCP lease time to a shorter value, such as 1 hour instead of 24 hours. This causes expired addresses to be returned to the pool faster, preventing pool exhaustion.
Disable MAC address filtering: If MAC filtering is enabled, the router blocks any device whose MAC address is not on the approved list. This can cause the DHCP handshake to fail silently. Temporarily disable MAC filtering to test whether it is the culprit.
Change the encryption type: Some routers have compatibility issues with certain encryption settings. If your router is set to WPA3 only, try switching to WPA2/WPA3 mixed mode. If it is on TKIP, switch to AES. These changes can resolve handshake failures that manifest as the obtaining IP address loop.
Clear the DHCP Cache on Rooted Android
For rooted Android devices, clearing the DHCP cache is a fix that goes deeper than a standard network reset. Use a root-capable file explorer and navigate to /data/misc/dhcp/. Delete every file in that directory. Also check /data/dhcp/ on some Android versions.
Another root-level fix involves permissions. Some users report that the file /system/etc/dhcpcd/dhcpcd-run-hooks loses its execute permission after an update. Use a root file explorer to set the permissions to 755 (read, write, execute for owner; read and execute for group and others). Reboot after making this change.
Update Router Firmware
Outdated router firmware is a common cause of DHCP compatibility issues, especially with newer devices. Check your router manufacturer’s website for firmware updates. Many modern routers can update directly from the admin panel. If your router is more than five years old and has not received a firmware update in over a year, it may not fully support modern DHCP standards.
If no firmware updates are available and the router is old, consider replacing it. Newer routers handle DHCP more reliably and support the latest WiFi standards, which eliminates a whole class of connection problems.
When Signal Strength Is the Real Problem
This is the most overlooked cause of the obtaining IP address loop. Most guides focus on DHCP settings and software fixes, but if your WiFi signal is weak, no amount of software tweaking will help.
DHCP packets are small, but they still need to travel between your device and the router clearly. If the signal is below about -75 dBm, packet loss becomes significant. The router sends a DHCP Offer, but your device never receives it cleanly. Your device sends a DHCP Request, but the router cannot read it. The handshake fails, and the loop begins.
To check signal strength on Android, use the WiFi analyzer feature in developer settings or download a free WiFi analyzer app. On Windows, type netsh wlan show interfaces in Command Prompt and look at the signal percentage. On macOS, Option-click the WiFi icon in the menu bar to see the RSSI value.
If your signal is below -75 dBm, the fix is physical. Move closer to the router, remove obstructions between your device and the router, switch from the 5 GHz band to the 2.4 GHz band (which reaches farther), or add a WiFi range extender to boost coverage in weak areas.
Systematic Troubleshooting Flow
When you have tried several fixes and nothing works, a systematic approach saves time. Follow this order:
Step 1: Toggle WiFi off and on. If it connects, you are done.
Step 2: Toggle airplane mode for 10 seconds. Try connecting again.
Step 3: Forget the network and reconnect with the password.
Step 4: Restart your device (phone, laptop, or console).
Step 5: Restart your router by unplugging it for 30 seconds.
Step 6: Check signal strength. If it is below -75 dBm, move closer or switch bands.
Step 7: Assign a static IP address on your device.
Step 8: Reset network settings on your device.
Step 9: Access the router admin panel and adjust DHCP pool size, lease time, and encryption type.
Step 10: Update router firmware or test with a different router to determine if the router is the problem.
If you reach Step 10 and still cannot connect, the issue may be hardware-related. Test your device on a completely different network (a friend’s house, a coffee shop, a mobile hotspot). If it connects there, the problem is your router or ISP. If it fails everywhere, your device’s WiFi hardware may need service.
Frequently Asked Questions
How do I fix obtaining an IP address problem?
Start by toggling WiFi off and on, then enable airplane mode for 10 seconds and disable it. If that does not work, forget the network and reconnect, restart your device, and restart your router. If the loop persists, assign a static IP address in your device’s network settings or reset your network settings entirely.
How do I force a device to release an IP address?
On Windows, open Command Prompt and run ipconfig /release followed by ipconfig /renew. On macOS, go to Network settings, select WiFi, click Details, and click Renew DHCP Lease under the TCP/IP tab. On Android and iOS, forgetting the network and reconnecting forces a new IP request.
What does it mean when my PS5 says it can’t obtain an IP address?
It means your PS5 sent a DHCP request to the router but never received a valid IP address response. This usually happens due to a weak WiFi signal, a router DHCP pool that is full, or an incompatibility between the PS5 and older routers. Try moving the console closer to the router, restarting the router, or manually setting a static IP in the PS5 network settings.
Why does my obtain IP address keep failing?
The most common causes are a router DHCP server running out of addresses, corrupted DHCP cache on your device, weak WiFi signal causing packet loss, or an incompatibility between newer devices and older routers. If the problem keeps coming back after a router reboot, the DHCP pool may be too small or the router firmware may need updating.
Why does a static IP work but DHCP does not?
A static IP works because it skips the DHCP handshake entirely. Your device already knows its IP address and does not need to ask the router for one. When DHCP fails, it means the four-step handshake between your device and the router is breaking at some point, usually due to a router configuration issue, MAC filtering, encryption mismatch, or signal degradation.
Conclusion
Fixing the obtaining IP address loop on a Wi-Fi network comes down to figuring out where the DHCP handshake is breaking. Start with quick fixes like toggling WiFi, airplane mode, and forgetting the network. Move to device-specific steps if needed, and finish with router-level adjustments like expanding the DHCP pool or assigning a static IP. Do not forget to check signal strength, as weak WiFi is a frequently overlooked cause that no software setting can fix. Follow the systematic troubleshooting flow if individual steps do not work, and you will resolve this problem in nearly every case.