This usually means the Intel AX201 joined the Wi‑Fi network, but Windows did not get a usable IP address from the router’s DHCP server. Start by checking whether Windows gave itself a `169.254.x.x` APIPA address, then renew the lease, and only after that move on to a network reset or router settings. If other devices are fine on the same Wi‑Fi, the laptop side is more likely; if nothing gets an address, check the router or ISP first.
Symptom
You can see the Wi‑Fi network name, and Windows may show that it is connected, but apps and web pages still fail to load. On an Intel AX201 laptop, that usually means the wireless link is up, but address assignment failed.
The error often appears right after connecting, after waking from sleep, or after a router restart. If the adapter is connected but the laptop cannot reach the router, the likely causes are DHCP, a local adapter state problem, or a router setting that blocks address assignment.
Before you start
Use the safest checks first. They show where the fault is without changing anything.
- Restart the PC first if only this laptop is affected.
- Restart the router or modem/router first if other devices on the same Wi‑Fi also cannot get online.
- Check whether airplane mode is off and whether Wi‑Fi is actually enabled.
- Stand close enough to the access point to rule out a weak signal or a bad band handoff.
- Test whether another device on the network gets a normal address.
- If the laptop can use Ethernet, check whether the wired connection works. That helps separate a Wi‑Fi problem from a wider internet problem.
If the laptop works on a phone hotspot or another Wi‑Fi network, the AX201 itself is less likely to be the root cause than the original router or network settings. If the problem follows the laptop across networks, keep going through the PC-side steps before you replace hardware.
Check whether Windows got an APIPA address
Before changing settings, confirm whether Windows assigned itself an APIPA address. APIPA is Windows’ fallback when DHCP fails, and it usually starts with 169.254.
- Open
Command Prompt. - Run the command.
ipconfig- Look for the Wi‑Fi adapter’s IPv4 address.
- If you see
169.254.x.xinstead of an address from your home network, Windows connected to Wi‑Fi but did not get a router address.
That result points away from a simple password or signal problem and toward DHCP, a router-side block, or a bad local network state. If you see a normal local address but still cannot browse, the problem may be DNS or router connectivity rather than IP assignment.
Renew the IP lease
Start with a release-and-renew cycle. This is the least disruptive fix, and it often clears a stale lease without touching drivers.
- Open
Command Prompt. - Release the current lease.
ipconfig /release- Renew the lease.
ipconfig /renew- Watch the result.
A fixed connection should come back with a normal local IPv4 address, a subnet mask, a default gateway, and DNS servers. If the command succeeds but the adapter still shows 169.254.x.x, or if the exact message varies and renewal still fails, move to a network stack reset. If ipconfig /renew says the DHCP server is unreachable, focus on the router side next.
Reset the Windows network stack
If renewing the lease does not fix it, reset the Windows network stack. This clears Winsock and TCP/IP state and can recover an adapter that looks connected but is stuck at the networking layer.
- Open
Command Promptas administrator. - Run the reset commands.
netsh winsock reset
netsh int ip reset- Restart the PC.
- Check Device Manager and make sure the Intel AX201 is enabled after the reboot.
After the restart, check the Intel AX201 driver state and adapter settings before you assume the hardware is bad. A recent driver update, a power-saving change, or an odd adapter setting can leave the card connected but unable to complete DHCP. In Intel community cases, users reported that uninstalling the Intel Wi‑Fi adapter in Device Manager and then scanning for hardware changes could restore connectivity, but that is more disruptive than a lease renew or stack reset and should stay later in the sequence. If the adapter also fails on a different Wi‑Fi network, keep the focus on the PC; if it works elsewhere, the router is more suspect.
Check Intel AX201 driver and adapter settings
If the reset did not help, look at the AX201 itself without jumping straight to a reinstall.
- Open Device Manager and confirm that the Intel AX201 is present and enabled.
- Check whether the driver was recently updated, especially if the failure started right after a Windows or vendor update.
- If the laptop has power-saving options for the wireless adapter, try disabling the setting that lets Windows turn off the device to save power.
- If the adapter has band or roaming settings exposed in Advanced properties, keep the defaults unless your laptop maker or Intel’s current documentation says otherwise.
Intel community threads show recurring AX201 failures where users had to remove the adapter in Device Manager and rescan hardware before it would connect again. In another case, Intel support asked for an SSU report because the issue kept returning. That does not prove the driver is always the cause, but it does show that a bad adapter state or driver problem can contribute. If the exact option labels have changed in Windows 10 or 11, check the current Intel and laptop-maker support pages before changing advanced settings.
Check the router and DHCP settings
If the laptop still cannot get a valid IP address, move to the router. DHCP is the piece that hands out local addresses, and several router settings can block it.
Check the router admin page for these items:
- DHCP server is turned on.
- The address pool still has free addresses.
- The lease limit is not too low for the number of devices on the network.
- MAC filtering or an access-control list is not blocking the laptop.
- Guest-network isolation or client isolation is not keeping the laptop from getting a normal lease.
- The router is not holding a reservation or static assignment conflict for the same address.
If the laptop works on a hotspot or another Wi‑Fi network but not at home, the home router is the best place to look first. If every device on the network is failing to get a lease, restart the router/modem and, if needed, ask the ISP whether the DHCP service on the gateway is working correctly. If you do not manage the router yourself, this is the point to hand it to the router admin rather than keep changing the PC.
Verify the connection is healthy
After a fix, confirm that the connection is actually healthy instead of just showing a Wi‑Fi icon.
- Run
ipconfigagain. - Check that the Wi‑Fi adapter now has a non-
169.254.x.xIPv4 address. - Confirm that a default gateway is listed.
- Open the router admin page if you know it.
- Open a normal website.
A healthy result means Windows got a real local address, the gateway is present, and the browser can reach the network normally. If the address looks right but websites still fail, test DNS separately before you assume DHCP is still broken. If the laptop only works after a manual adapter reset and the problem keeps coming back, that is a sign to escalate rather than keep cycling the same steps.
When to escalate
Escalate to the router admin if you do not control the network settings, or if you suspect DHCP, MAC filtering, or lease limits and cannot verify them yourself. Escalate to the ISP if the router cannot hand out addresses to any device, or if the gateway itself is unstable.
Consider hardware replacement only after the laptop fails on multiple networks, survives a network stack reset, and still shows the same DHCP problem after a clean driver check. If the issue stays limited to one laptop and one router, the router side is still the more likely target. If it stays with the laptop everywhere, check the laptop maker’s current BIOS and wireless support pages before replacing the AX201.
Frequently Asked Questions
Should I restart the router or the PC first?
Restart the PC first if only the Intel AX201 laptop is affected. That keeps the change local and easy to reverse. If multiple devices on the same Wi‑Fi cannot get addresses, restart the router or modem/router next, because the DHCP service or address pool is more likely at fault.
Sources
- Intel(R) Wifi 6 AX201 stops working and constantly requires network resets - Intel Community (community.intel.com)
- Intel(R) Wi-Fi 6 AX201 160MHz driver repeatedly failing - Intel Community (community.intel.com)