Device Not Getting IP Address From Router — step-by-step DHCP & Wi-Fi fix
Joe B.
Expert ★★★★★ 27,853 satisfied customers
Specialities: Home networking, Wi-Fi routers, modems, Windows/macOS internet issues, DHCP & IP configuration, ISP setup
Fix device not getting IP address from router — DHCP not working, Wi-Fi valid IP error, 169.254 address
Technician
On the problem device, do you see messages like “Wi-Fi doesn’t have a valid IP configuration”, “Failed to obtain IP address”, or “No valid IP configuration”? When you check the IP details, does it show a strange address starting with 169.254.x.x or no IP at all?
Also, is it just this one laptop/phone that can’t get an IP from the router, or do several devices (phones, smart TV, consoles) fail to connect properly? And if you log in to your router, do other devices appear in the DHCP client list with normal IP addresses (like 192.168.0.x or 192.168.1.x)?
Other devices are fine: my work laptop and smart TV both get internet from the same TP-Link router. In the router admin page I can see them in the DHCP clients list, but the problem laptop doesn’t show up there at all, like it’s not getting an IP from the DHCP server.
Technician
Common reasons for a device not getting IP address from router are:
• The router’s DHCP server is off or its address pool is exhausted, so new devices can’t get an IP.
• The device has static IP or manual DNS settings that don’t match the router’s network.
• Corrupted Wi-Fi profile, VPN, or security software is blocking DHCP traffic from the router.
• MAC filtering or access control on the router is silently blocking that device.
We’ll check both sides: first your router’s DHCP configuration, then the laptop’s IP / DNS / adapter settings so it successfully obtains a valid IP address from the router again.
On the laptop I already tried “Forget network,” reconnecting, and the Windows troubleshooter. It just says “DHCP is not enabled for Wi-Fi” or that it couldn’t fix the problem. Still stuck on 169.254 after reboot.
Technician
Step A — Make sure the laptop is allowed to get an IP automatically
1) On the Windows 11 laptop, open Network & Internet → Advanced network settings → More network adapter options and right-click your Wi-Fi adapter → Properties.
2) Double-click Internet Protocol Version 4 (TCP/IPv4) and set both to:
• Obtain an IP address automatically
• Obtain DNS server address automatically
so it can get its IP and DNS from your router’s DHCP server.
3) Click OK to close all windows.
Now we’ll force it to request a fresh IP from the router:
4) Open Command Prompt as administrator and run, in this order:
•
ipconfig /release•
ipconfig /renewAfter
/renew, check whether the laptop now shows a 192.168.1.x address and appears in the router’s DHCP client list. If it still sticks to 169.254 or says “unable to obtain IP address from DHCP server”, we’ll clear the Wi-Fi profile and check for any router-side blocking next.ipconfig /release worked, but ipconfig /renew gave an error about being unable to contact the DHCP server. The IP went back to 169.254 and still no entry for this laptop in the router’s client list.I also use a VPN client sometimes, but it was closed when I tested this.
Technician
Step B — Double-check router DHCP and access rules
• In your TP-Link router, under DHCP settings, confirm that:
– DHCP Server is Enabled.
– The DHCP range is on the same subnet as the router (for example router 192.168.1.1 and range 192.168.1.100-192.168.1.199).
– There aren’t any Reserved IPs using the same address as the laptop.
• Check Wireless → MAC Filtering / Access Control. If it’s enabled, make sure your laptop’s MAC address is allowed, or temporarily disable access control to test.
Step C — Reset the Wi-Fi profile on the laptop
1) In Windows, go to Settings → Network & Internet → Wi-Fi → Manage known networks, remove your home SSID, then add it again from scratch.
2) Temporarily disable any VPN client and third-party firewall/antivirus that might intercept DHCP packets.
3) Reconnect to Wi-Fi and watch the IP: if it now gets a 192.168.x.x address, the device is finally getting an IP from the router and the “Wi-Fi doesn’t have a valid IP configuration” message should disappear.
Now the laptop finally shows 192.168.1.112 with the right gateway and DNS, and it appears in the router’s DHCP list. Internet is working on that laptop again. But my Android phone sometimes still hangs on “Obtaining IP address…” when I connect to the same Wi-Fi.
Technician
For the Android phone stuck on “Obtaining IP address” or “Failed to obtain IP address” from the router:
Step D — Refresh Wi-Fi and DHCP for mobile devices
• On the phone, go to the Wi-Fi network, choose Forget, then reconnect and re-enter the password so it requests a fresh IP from the router.
• In Advanced Wi-Fi settings, make sure IP settings are set to DHCP (not Static), otherwise the device won’t dynamically get an IP address from your router.
• If your router has separate SSIDs for 2.4 GHz and 5 GHz, test both. Some phones are picky and fail to get an IP on one band if the security or channel is odd.
• In the router’s DHCP settings, slightly extend the lease range (for example 192.168.1.50-192.168.1.250) so there’s no chance the pool is running out when many devices connect.
Once the phone gets a regular 192.168.x.x address, it’s no longer a device not getting IP from router problem — it behaves like your other working clients.
One more thing: I have a wired gaming PC that sometimes says “Ethernet doesn’t have a valid IP configuration”. It’s connected directly to the same router by cable. Usually rebooting the PC fixes it, but it keeps coming back.
Technician
To stabilise the gaming PC:
• Confirm the PC’s Ethernet adapter is also set to Obtain an IP address automatically and Obtain DNS server address automatically in IPv4 settings.
• Try a different Ethernet cable and LAN port on the router to rule out physical issues that could interrupt DHCP packets.
• Update the PC’s network adapter driver from the motherboard or NIC manufacturer — outdated drivers often cause sporadic “no valid IP configuration” errors.
• In the router, make sure there isn’t a conflicting static IP reservation for that MAC address that’s outside the DHCP range.
If the router is old or overloaded, a quick router reboot plus a firmware update can also fix intermittent DHCP problems where some devices don’t get IPs while others work fine.
So now the laptop, phone, and gaming PC all get IP addresses from the router. Is there anything else I should change to keep this “device not getting IP address from router” issue from happening again?
Technician
Step E — Prevent future “device not getting IP from router” problems
• Turn on automatic firmware updates on the router if available, or check for firmware updates every month or two; many updates specifically address DHCP not working or random disconnects.
• Keep your DHCP range large enough for all devices and guests — for example, a pool of at least 100 addresses on a home network.
• For important devices (work PC, NAS, printer, gaming PC), consider setting up DHCP reservations so they always receive the same IP address from the router without using manual static IPs.
• Avoid mixing many manual static IPs inside the same range as DHCP; if you do use static addresses, place them outside the router’s DHCP pool.
• Periodically review the DHCP client list and remove any very old reservations or devices you no longer use, so they don’t clutter or conflict with current clients.
With these tweaks, your router should consistently assign IP addresses and you’re far less likely to see “Wi-Fi/Ethernet doesn’t have a valid IP configuration” again.
This was way clearer than the random tips I found before. Thanks for walking me through the DHCP and IP settings step by step.
Technician
Summary: To fix a device not getting IP address from router, make sure the router’s DHCP server is enabled, its IP pool matches the LAN subnet, and there’s no MAC filtering blocking the device. On the device, set IPv4 and DNS to automatic, clear old Wi-Fi profiles, and disable VPN/firewall temporarily. After a release/renew it should receive a valid IP (not 169.254) and reach the internet through the router.
If you ever see “Failed to obtain IP address” or “doesn’t have a valid IP configuration” again, you can open a chat with an expert and we’ll trace the problem live with you.
Technician
Quick answer: the accepted fix
Accepted fix when a device is not getting an IP address from the router: confirm the router’s DHCP server is enabled and the IP range matches the LAN network, then reboot the router, set the device’s IPv4 and DNS to obtain automatically, and run a DHCP renew so the device drops any 169.254 address and receives a valid IP (for example 192.168.x.x) from the router.
Why devices stop getting an IP address from the router (DHCP, Wi-Fi, Ethernet)
Most home device not getting IP address from router problems are DHCP-related, not full internet outages. If DHCP fails, your laptop or phone either sticks at “Obtaining IP address”, shows “Wi-Fi doesn’t have a valid IP configuration”, or falls back to a 169.254.x.x APIPA address. That means the device never received a valid IP lease from the router.
Typical causes include: the router’s DHCP server disabled, IP pool too small or mis-matched with the LAN subnet, devices set to static IP with wrong gateway, or security features like MAC filtering and captive portals interfering with DHCP. By tracing the path device → router (DHCP) → modem → ISP, you can see whether the problem is simply that the router isn’t assigning IPs even though the internet connection itself works.
How to tell if the IP problem is your device, router DHCP, or cable
To quickly narrow down a device not getting IP address from router issue, test more than one device:
If other phones and computers happily get 192.168.x.x addresses from the router while one laptop shows 169.254 or “no valid IP configuration”, the problem is almost always that device’s adapter, drivers, or IP/DNS settings. If several devices on Wi-Fi and Ethernet can’t get IPs, log into the router and check whether the DHCP server is running, the address pool is valid, and there aren’t two DHCP servers fighting each other on the same network (for example, ISP modem plus your own router).
Device not getting IP address from router — quick troubleshooting tips
Confirm DHCP on the router, then reset device IP and Wi-Fi/Ethernet settings.
Fast path: make sure only one DHCP server is active on your network → verify the router’s LAN IP and DHCP range are on the same subnet → reboot router and affected devices → on each device, set IPv4/DNS to obtain automatically and forget/rejoin Wi-Fi → use ipconfig /release and ipconfig /renew on Windows to force a fresh lease. Keeping firmware and drivers updated helps avoid recurring “doesn’t have a valid IP configuration” errors.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model and devices, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts for device not getting IP address from router, Wi-Fi valid IP configuration errors, DHCP not working, and more.
Expert will respond in minutes
We match you with a networking specialist who knows DHCP servers, IP addressing, Wi-Fi routers, and Windows/Android “failed to obtain IP address” fixes for all major brands (Netgear, TP-Link, ASUS, Linksys and more).
Save time & money
Stop guessing why a device can’t get an IP from your router or endlessly rebooting equipment. Get a clear step-by-step DHCP & IP fix in chat and get every device back online quickly.
FAQ
Why is my device not getting an IP address from the router?
Usually the router is powered on but its DHCP settings are wrong or your device is misconfigured. Common issues include the router’s DHCP server being disabled, the IP address pool not matching the LAN subnet, another device acting as a second DHCP server, or the client being set to a manual/static IP that doesn’t fit your network.
How do I fix “Wi-Fi doesn’t have a valid IP configuration”?
On Windows, set the Wi-Fi adapter’s IPv4 and DNS to “Obtain automatically”, then run ipconfig /release and ipconfig /renew in Command Prompt. On the router, make sure DHCP is enabled, the pool is big enough, and there’s no MAC filtering blocking the device. After reconnecting to Wi-Fi, your device should receive a normal private IP address (for example 192.168.x.x).
What does a 169.254.x.x IP address mean?
A 169.254.x.x address is an automatic private IP (APIPA) assigned by Windows or other systems when the device cannot obtain an IP address from any DHCP server. It means your router didn’t reply to the IP request, so you should check DHCP settings on the router and the device’s adapter configuration.
When should I reset my router if it’s not assigning IP addresses?
If you’ve confirmed cables are good, DHCP is enabled, the IP pool is valid, and devices are set to obtain an IP automatically but the router still won’t hand out IP addresses to any clients, a factory reset can clear a bad configuration. Press and hold the reset button as the manufacturer describes, then rerun the setup wizard and re-enable DHCP and Wi-Fi from scratch.
Sources
- Microsoft — DHCP client can’t obtain a valid IP address
- TP-Link — What to do if your client cannot obtain an IP address
- Surfshark — Failed to obtain IP address: causes and fixes
Filed under: Internet & Wi-Fi Troubleshooting
Related articles
- Spectrum Unable to Login to Router — step-by-step admin page fix
- Spectrum Router Not Broadcasting Wi-Fi — step-by-step network fix
- Spectrum Wi-Fi Connected but No Internet — step-by-step fix
- Xfinity Router Keeps Restarting — step-by-step reboot & stability fix
- Xfinity Wi-Fi Connected But No Internet — step-by-step fix
- Xfinity App Not Detecting Gateway — step-by-step xFi fix
- Xfinity No Internet After Outage — step-by-step fix
- Online games lagging on Wi-Fi — step-by-step ping & lag spike fix