If your Intel AX211 joins Wi‑Fi but Windows says it cannot get a valid IP address, the wireless link is up, but DHCP is not handing out a usable IPv4 address, gateway, or lease. Start by checking whether the problem follows the laptop, the router, or a stale lease. Then try reversible fixes like renewing the address or reconnecting before you touch drivers or router settings. In practice, start with the adapter state, then the lease, and only then move to driver or router changes.
What this error means when Wi‑Fi says connected but nothing works
This message usually means Windows connected to the access point, but the network handoff never finished. The AX211 can look connected while still missing a usable IPv4 address, default gateway, or DHCP reply, so the browser has no real path out to the internet.
That is why you can see strong signal and still get no usable network. A stale lease, a broken saved profile, router DHCP trouble, or an adapter problem can all look similar at first. Intel user reports also show that the AX211 can connect while DHCP fails, or stay connected while traffic never reaches the router.
Before you start
Use a quick pattern check before changing settings. If only this laptop fails on one Wi‑Fi network, the problem is usually local to the adapter, the saved Wi‑Fi profile, or the lease state. If several devices fail on the same network, the router side is more likely. If it happens after sleep, reconnect, or a reboot, a stale lease or stuck adapter state is a common fit.
| What you see | What to check first |
|---|---|
| Only the AX211 laptop fails | Laptop, saved profile, adapter settings |
| Many devices fail | Router DHCP or router config |
| It works after reboot, then breaks again | Lease or adapter state |
| One network fails, others work | That network’s router or profile |
Before you change anything more drastic, check these safe points:
- Confirm whether ethernet works on the same PC. If ethernet works, the laptop is not globally offline.
- Confirm whether other devices on the same Wi‑Fi can get online. If they can, the router is not the only suspect.
- Make sure you can get back into the network if you forget it. If this is a work or school network with special login details, have those ready first.
If the laptop fails on more than one Wi‑Fi network but ethernet still works, that starts to point more toward the AX211 driver or adapter settings than the router.
The safest fixes to try first on the Windows laptop
Start with the smallest reversible changes. Use this order: reset the adapter state, renew the IP lease, then forget and rejoin the network if the saved profile may be stale. Those steps usually show whether you are dealing with a lease problem or something deeper.
- Disable and re-enable the AX211 adapter.
Open Device Manager, find the Intel AX211 under Network adapters, disable it, wait a few seconds, then enable it again. This can clear a stuck radio or DHCP state without changing your saved settings.
- Renew the IP address.
Open Command Prompt and run:
ipconfig /release
ipconfig /renewIf DHCP was only stuck, Windows should request a fresh lease and the connection should become usable again. If ipconfig /renew fails or comes back without a valid IPv4 address, that points away from a simple lease hiccup and toward the adapter settings or the router side.
- Forget the Wi‑Fi network and reconnect.
Use this when the saved profile may be corrupt, mismatched, or carrying bad connection details. Forgetting the network clears the stored profile, which can help when Windows keeps reusing a bad saved entry. If the router’s DHCP service is broken, though, forgetting the network will not fix the underlying handoff.
- Check the adapter’s IP settings.
Make sure the AX211 is set to obtain an IP address automatically and obtain DNS automatically. Also check that you have not set a manual IPv4 address, a static gateway, or a custom DNS value on only that adapter. A bad manual value can block assignment on one network while other adapters still work.
- Stop if the issue is clearly not local.
If the adapter still cannot get a usable address after a renew and a reconnect, the next move is to compare it on another known-good Wi‑Fi network before you reach for broader resets. That comparison tells you whether you are chasing a laptop problem or a network problem.
When router settings are the real cause
If only one device fails while other devices on the same Wi‑Fi work, the router is still worth checking. The most common router-side causes are DHCP being off, the address pool being exhausted, a lease table that is full or stale, or a MAC filter that blocks the AX211 laptop.
Look for these checks in the router admin page:
- DHCP server is enabled.
- The DHCP address range still has free addresses.
- The laptop is not blocked by MAC filtering, access control, or parental controls.
- The router has not pinned the laptop to a bad reserved address.
- The router is not overloaded with stale leases after many reconnects.
If the router hands out addresses to other devices but not this one, compare the laptop’s MAC address entry, reserved lease, and access-control rules. A bad reservation can make one client look broken while everything else seems fine. If the router is an ISP-supplied unit and you recently added another access point, test the laptop on the other access point first. That helps separate a router DHCP problem from an AX211-specific issue.
If you reboot the router, treat that as a test, not a final fix. If the laptop gets an address again after the reboot but then loses it later, the lease table or DHCP service is still suspect.
How to confirm the problem is actually solved
The fix is real only when Windows shows a valid IPv4 address and traffic actually passes through the gateway. Open Command Prompt and run ipconfig, then check the Wi‑Fi adapter section for an IPv4 address that fits your network, a default gateway, and DNS servers. If the adapter shows an address like 169.254.x.x, that usually means Windows still did not get a proper DHCP lease.
ipconfigA good result is a normal private IPv4 address on the Wi‑Fi adapter, a listed default gateway, and a website loading in a browser without delay. If ipconfig looks right but web pages still fail, the problem may have shifted from DHCP to DNS or gateway reachability.
If the AX211 still fails after the basic checks, compare it on another known-good Wi‑Fi network. If it fails there too, the driver or adapter settings become more likely. If it works elsewhere but not on one router, stay focused on router DHCP, lease reservations, and access rules. Intel user reports also suggest that a driver change can matter when the failure follows the laptop across networks, especially when the adapter looks healthy in Windows but traffic still stalls.
What to do next if the AX211 still fails
If the adapter still will not get a usable address after the safe checks, isolate the fault cleanly instead of trying every fix at once. Test the laptop on a second Wi‑Fi network, then compare that result with ethernet if you can. If the AX211 fails across different networks, that makes a driver or adapter issue more likely; if it only fails on one network, keep your attention on that router’s DHCP, lease, and access-control settings.
A driver update makes sense when the problem follows the laptop across networks, especially if the connection drops after sleep or reconnects unpredictably. If the adapter only fails on one SSID and works elsewhere, keep working the router side before reinstalling drivers.
Conclusion
If the AX211 still cannot get a usable address after these checks, compare it on another Wi‑Fi network. Then decide whether the next move should be a driver change or a router-side fix.
Frequently Asked Questions
Should I forget the network or renew the lease first?
Try `ipconfig /release` and `ipconfig /renew` first, because that is the smallest reversible fix for a stale DHCP lease. Forget the network next if the lease renew does not help or if the saved Wi‑Fi profile may be corrupt. That keeps the first step simple and avoids wiping a profile too soon.
When is a network reset the right move?
Use a Windows network reset only after the lighter fixes fail, because it changes more than a simple lease renew or Wi‑Fi reconnect. It is most useful when the adapter still will not get a usable IPv4 address after you have checked the router, the profile, and the adapter’s automatic IP settings.
How do I know if this is a driver issue instead of the router?
It points toward the driver or adapter when the AX211 fails on multiple Wi‑Fi networks, but the same laptop works by ethernet. If only one router or one SSID fails, the router side is still the better place to look first. That split usually tells you which path to follow next.
Sources
- How to Fix 'WiFi Doesn't Have a Valid IP Configuration' on Windows (oneuptime.com)
- Intel wifi 6e ax211 doesn't obtaining DHCP on WiFi / Looses connection if it gets an IP - Intel Community (community.intel.com)
- Intel Wi-Fi 6E AX211 - Connected to Wi-Fi but cannot communicate with router - Intel Community (community.intel.com)
- Intel(R) Wi-Fi 6E AX211 160MHz Problem Status: 0xC00000E5 - Intel Community (community.intel.com)
- intel(R) wi-fi 6e ax211 160mhz invalid ip / cannot connect to dhcp - Intel Community (community.intel.com)