A PCIe Wi‑Fi card that shows “connected without internet” usually has a working wireless link to the router. The failure is usually farther along: DHCP, the default gateway, DNS, the router itself, or the ISP. Start by checking whether the PC can reach the router, then whether it can reach the internet by IP, then by name. That shows which layer broke, so you can fix the right setting instead of resetting everything blindly.
What Windows is really saying
Windows is telling you the Wi‑Fi adapter joined the router, but internet traffic is not flowing normally. That is not the same as a dead card. The radio link can be up while IP address assignment, the default gateway, DNS, router access, or ISP access is broken.
A simple way to think about it is:
- Wi‑Fi association: the card connects to the router.
- DHCP: the router hands out an IP address, subnet mask, gateway, and usually DNS.
- Gateway: Windows knows where to send traffic outside your local network.
- DNS: Windows can turn a name like
example.cominto an IP address. - Internet reachability: traffic gets past the router and out to the web.
If any one of those layers fails, Windows can still show a connected Wi‑Fi icon while websites fail to load.
Symptom: how this usually looks
You’ll often see the PC say it is connected to the Wi‑Fi network. But browsers spin, apps fail to load, or Windows marks the network as having no internet access. Sometimes other devices on the same Wi‑Fi work normally, which makes this one desktop look broken even though the router is fine. In a few cases, the PC can join the network, but only some sites work. The connection can also drop as soon as the adapter switches band or mode. People sometimes report the issue with PCIe cards such as the TP-Link WiFi 6 AX3000 PCIe WiFi Card (Archer TX3000E) or Intel AX200-based adapters, but that does not prove the card is bad by itself.
Before you start
Before you change anything, separate a PC problem from a router or ISP problem.
- If every device on the same Wi‑Fi has no internet, look at the router or ISP first.
- If only this PC fails and other phones or laptops work, focus on Windows, the driver, the adapter, or the PC’s network settings.
- If this PC works on another Wi‑Fi network, the card is less likely to be dead and the home router setup becomes the stronger suspect.
A good quick check is to open the router’s admin page and see whether the PC appears connected and active. That only proves the association exists. It does not prove the router is handing out a usable address or forwarding traffic correctly. A user report with both phone and PC failing on one network while other networks worked fine is a classic sign that the fault can sit in the local router setup rather than the devices themselves.
Check the PC, the router, and the ISP in that order
Use the quickest tests first, and stop as soon as one layer fails.
| Test | What you do | What it means if it passes | What it means if it fails |
|---|---|---|---|
| Ping the router | Ping the default gateway from ipconfig /all | The PC can reach the router over Wi‑Fi | The local Wi‑Fi link, antenna, driver, or adapter settings are the likely problem |
| Ping a public IP | Ping 8.8.8.8 | The PC can reach the internet by address | The problem is probably router, modem, or ISP, not DNS |
| Open a website by name | Try google.com or another site | DNS is working | DNS is failing even if raw internet access works |
Start with ipconfig /all and look at the wireless adapter section.
ipconfig /allYou want to see:
- an IPv4 address in your home network range,
- a subnet mask,
- a default gateway,
- at least one DNS server.
If the IPv4 address starts with 169.254, Windows did not get a proper address from DHCP. If the default gateway is blank, the PC may be connected to Wi‑Fi but has nowhere to send traffic beyond the local network. If the gateway exists but sites do not open, DNS may be the weak point.
Now test the layers separately.
ping 8.8.8.8ping google.comIf the router responds but 8.8.8.8 does not, that points away from the PC and toward the router, modem, or ISP path. If 8.8.8.8 works but google.com fails, the internet path is there and DNS is the problem. If even the router does not respond to ping, stay focused on the PC side first: driver, power, antenna, or adapter seating.
Fix the most likely causes first
- Turn Wi‑Fi off and back on in Windows, or disable and re-enable the adapter from Network Connections.
- Reboot the router. If you have a separate modem or ISP gateway, power-cycle that too, then test the PC again before changing anything else.
- Check the Wi‑Fi adapter driver in Device Manager. If the problem started after a driver update, roll it back. If it started before that, install the latest stable driver from the card maker or chipset maker for your Windows version. Then check the current release notes or support page in case the exact package has changed since your last install.
- Open the adapter’s properties in Device Manager and check power management. If Windows is allowed to turn off the device to save power, disable that option and test again.
- Open the router’s admin page and check for DHCP issues, MAC filtering, access control, guest-network isolation, or a DNS setting that points to a bad resolver. A router can show the PC as connected while still refusing to hand out a usable address or blocking traffic in a way that looks like a PC problem.
- If the PC gets an address but websites still fail, compare the router test and the public IP test. If the PC can reach the router but not
8.8.8.8, the issue is beyond the PC. If the PC can reach8.8.8.8but not site names, fix DNS on the router or in Windows.
- Only after those checks fail, use a Windows network reset. That can clear a tangled network stack, but it is overkill if the issue is just a bad DNS setting or a driver problem. Use it when the PC’s network config looks corrupted, not as the first move.
A small but useful clue: if the router admin page shows the device as connected and active, that still doesn’t rule out DHCP or DNS failure. It only shows the Wi‑Fi association exists. One common pattern is a router that lets the device join but doesn’t give it a usable route out. The connection looks healthy until you try to load anything.
When to suspect hardware, signal, or antenna trouble
If the card joins the network but traffic stalls, drops, or never reaches the router consistently, start thinking about hardware or RF trouble. That includes a poorly seated PCIe card, loose antenna leads, antennas left disconnected after installation, heavy interference, or a failing adapter.
A weak signal can be misleading because the Wi‑Fi icon still says connected. If the PC is far from the router, tucked behind a metal case, or using the wrong antenna position, the link may associate but perform badly enough that real traffic collapses. In practice, that can look like DNS or ISP trouble when it is really a physical link problem.
If the same card works on another Wi‑Fi network, the hardware is less likely to be dead. If another adapter or another PC works fine on the same router, the problem is more likely in this card, its driver, or how this PC is set up. There are also reports of certain adapter and mode combinations behaving differently, including cases where changing the Wi‑Fi mode changed whether internet access worked. That is a clue, not proof, so test the adapter settings rather than treating it as a final diagnosis.
Verify the fix
After each change, test in the same order: router ping, public IP ping, then a website by name.
ping <your-router-gateway>ping 8.8.8.8ping google.comIf the gateway ping works, the local Wi‑Fi link is back. If 8.8.8.8 works, the PC can reach the internet. If google.com works too, DNS is also healthy and the fix is done. If only the first test works, the router or ISP path still needs attention. If the first two work but names do not, fix DNS next.
Frequently Asked Questions
Why does Windows say connected with no internet when the Wi‑Fi bars look fine?
Because the radio link is up, but something after that link is broken. The usual causes are a missing or bad default gateway, DHCP failure, DNS failure, router filtering, or an ISP outage, so the Wi‑Fi bars alone do not prove internet access.
Should I reset Windows network settings right away?
No. A reset is a last-step repair, not the first test. Check the IP address, default gateway, DNS, driver state, and router status first. Those results usually show what needs fixing without wiping useful settings.
Sources
- Quest 2 - Connected to wifi but suddenly "No Internet" | Community (communityforums.atmeta.com)
- Intel AX200 Wifi 6 pcie card 5Ghz - No internet. | Overclockers UK Forums (forums.overclockers.co.uk)
- Connected to wifi without internet. : r/HomeNetworking (reddit.com)