How to Fix WiFi DHCP Errors: “Failed to Obtain IP Address” and Related Issues

The “Failed to Obtain IP Address” error is one of the most frustrating WiFi messages you can encounter. Your device shows a full signal bar, you enter the correct password — and then nothing. Understanding why DHCP errors happen makes them straightforward to fix.

What Is a DHCP Error?

DHCP stands for Dynamic Host Configuration Protocol. Every time a device joins your WiFi network, it broadcasts a request asking “what IP address should I use?” Your router’s built-in DHCP server answers by assigning a unique address from its available pool. A DHCP error means that handshake broke down — your device never received a valid IP address, so it cannot route traffic and the connection fails.

Related error messages you might see include: Obtaining IP Address (stuck loading), IP Configuration Failure, DHCP lookup failed, and No valid IP configuration on Windows.

Common Causes

• Full DHCP pool: Your router has a limited range of IP addresses it can hand out (e.g., 192.168.1.2 – 192.168.1.50). If every address is in use, new devices are turned away.
• DHCP server disabled: Router factory resets, firmware updates, or accidental misconfiguration can silently disable the DHCP server.
• IP address conflict: Two devices have claimed the same IP, causing both to fail intermittently.
• MAC address randomization: Android 10+ and iOS 14+ randomize MAC addresses by default, which can confuse routers configured with MAC-based reservations or filtering.
• Weak signal: The device hears the WiFi network but the signal is too weak to complete the DHCP handshake reliably.
• Outdated drivers or firmware: Buggy network drivers on Windows or outdated router firmware can corrupt DHCP negotiation.

Fix 1: Restart Your Router, Modem, and Device

A stale DHCP lease table or a temporarily crashed DHCP service is cleared by a full power cycle. Unplug your modem and router from power, wait 30 seconds, then plug the modem in first. Once it syncs (usually 60 seconds), plug in the router. After the router finishes booting, restart the device showing the error. This single step resolves the majority of DHCP failures.

Fix 2: Forget the Network and Rejoin

A corrupted saved network profile can store a conflicting static IP or bad credentials. On Android: Settings → WiFi → long-press the network → Forget. On Windows: Settings → Network & Internet → WiFi → Manage known networks → Forget. Rejoin the network fresh and let DHCP assign a clean address.

Fix 3: Verify DHCP Is Enabled on Your Router

Log into your router admin panel (typically 192.168.1.1 or 192.168.0.1 in any browser) and navigate to the LAN or DHCP settings page. Confirm that the DHCP server toggle is On and that a valid address range is configured — for example, 192.168.1.100 to 192.168.1.200. Save changes and reboot the router.

Fix 4: Expand the DHCP Address Pool

If you have many devices on your network — phones, laptops, smart home gadgets — the default pool of 50 addresses fills quickly. In your router’s DHCP settings, widen the ending address (e.g., change the pool end from 192.168.1.150 to 192.168.1.254) to accommodate more devices. Also reduce the lease time from 24 hours to 2–4 hours so addresses from disconnected devices are recycled faster. See our guide on smart home devices slowing down WiFi for more on managing large device counts.

Fix 5: Disable MAC Address Randomization (Android)

Android 10 and later use a randomized MAC address for each WiFi network by default. This privacy feature can trigger DHCP failures on routers that use MAC-based IP reservations or MAC filtering. To switch to your device’s real MAC address: Settings → WiFi → tap the network name → Privacy → Use device MAC. Reconnect after changing this setting.

Fix 6: Assign a Static IP Address (Device-Side)

If DHCP keeps failing on a specific device, bypass it entirely by assigning a static IP in the device’s network settings:

• Android: Settings → WiFi → tap network → Edit → Advanced → IP Settings: Static. Set IP address to 192.168.1.20, Gateway to 192.168.1.1, DNS 1 to 8.8.8.8, DNS 2 to 8.8.4.4.
• Windows: Settings → Network & Internet → WiFi → Hardware properties → Edit IP assignment → Manual. Enter the same values.

Choose an IP address outside the router’s DHCP pool to avoid future conflicts.

Fix 7: Reset the TCP/IP Stack (Windows)

On Windows, a corrupted network stack can prevent DHCP from functioning even when the router is healthy. Open Command Prompt as Administrator and run these commands in order:

1. netsh int ip reset
2. netsh winsock reset
3. ipconfig /release
4. ipconfig /flushdns
5. ipconfig /renew

Restart Windows after running all five commands. This resets the TCP/IP stack to factory defaults and forces a fresh DHCP lease request.

Fix 8: Disable MAC Filtering on the Router

Some routers have a MAC address filter or access control list that only allows pre-approved devices to connect. If your device’s MAC address (or randomized MAC) isn’t on the whitelist, the router silently drops its DHCP request. In your router admin panel, look for Access Control, MAC Filter, or Wireless MAC Filtering and either disable the feature or add your device’s MAC address to the allowed list.

Fix 9: Update Network Drivers and Router Firmware

Outdated drivers are a known cause of DHCP negotiation failures on Windows laptops. Open Device Manager → Network Adapters, right-click your WiFi adapter, and select Update driver. For your router, log into the admin panel and check for a firmware update — manufacturers regularly release patches that fix DHCP-related bugs. Our router firmware update guide walks through the process for every major brand.

Quick Diagnostic Checklist

• Router and modem power-cycled in the correct order (modem first).
• DHCP server confirmed enabled in router admin panel.
• DHCP address pool is large enough for all connected devices.
• Network forgotten and rejoined on the failing device.
• MAC address randomization disabled on Android/iOS.
• MAC filtering checked and device added to whitelist if needed.
• Static IP set on the device as a fallback.
• TCP/IP stack reset on Windows.
• Router firmware and device network drivers up to date.

If the error persists on every device simultaneously, the problem is almost certainly on the router itself — try a factory reset as a last resort. For deeper network diagnostics, see our guide on fixing WiFi IP address conflicts and our DNS error troubleshooting guide.