If your Windows PC can ping the router but not the internet, the problem is usually not the Wi-Fi link itself. It’s usually DNS, a Windows setting that changes how traffic is sent, or a router, modem, or ISP problem beyond the gateway. Start with three tests: ping the router, ping a public IP, then resolve a domain name. That tells you which layer failed before you change anything.
Start with the three tests that separate the layers
These three tests are the quickest way to tell whether the fault is local, DNS-related, or upstream. Run them in order.
| Test | What it proves | What a failure usually means |
|---|---|---|
| Ping the router | Your PC can reach the local gateway | Local network issue, wrong gateway, or adapter problem |
| Ping a public IP | Raw internet reachability without DNS | Routing, WAN, modem, router, or ISP problem |
| Resolve a domain | DNS name lookup | DNS server, DNS suffix, proxy/VPN, or policy problem |
- Ping your default gateway, which is usually your router’s local IP.
ping 192.168.1.1If this works, your PC can reach the router on the local network. If it fails, stop here and fix the local connection first.
- Ping a public IP address that does not depend on DNS.
ping 8.8.8.8If this fails but the router ping worked, the break is beyond local LAN access. That points away from DNS and toward routing, the router WAN, the modem, or the ISP.
- Resolve a domain name with
nslookup.
nslookup example.comIf the public IP ping works but nslookup fails, you likely have a DNS problem. Microsoft notes that nslookup uses the client’s configured DNS server, not the local cache. That makes it the right check when you want to know what Windows is actually asking.
What each result actually means
The pattern matters more than any single failed ping. A router ping only proves that your PC can talk to the gateway. It does not prove the router can reach the internet.
If the router ping works and the public IP ping fails, treat it as a routing or WAN problem first. The PC is reaching the router, but traffic is not getting past it.
If the public IP ping works and names fail, focus on DNS. In practice, that often means Windows is using the wrong DNS server, the DNS server can’t be reached, or a policy is steering lookups somewhere else.
If public IPs and names both work but websites still misbehave, check the browser path next. A proxy, VPN, or DNS policy can make one app fail while everything else looks normal.
If one website loads and you assume the problem is gone, be careful. One successful page can be a cached result or a route that only happens to work once. It is not enough to prove the whole stack is healthy.
Windows settings that can fake a DNS problem
Check the Windows side before you touch the router. Some settings change lookup behavior or redirect traffic, and they can look like a DNS fault. I’ve seen people spend an hour on DNS when the real issue was a leftover proxy, a VPN client, or a policy that only affected part of the traffic.
Start by checking the active DNS server. Run:
ipconfig /allLook for the DNS Servers line on the active adapter. If it points to something stale, something on a VPN adapter, or something you don’t recognize, that’s a strong clue. If nslookup shows a different answer than you expected, compare that output with the adapter settings.
Then check for a proxy. Windows can use a manual proxy or an automatic configuration script, and either one can send browser traffic somewhere unexpected even when ping still works. Also check whether a VPN client is installed, connected, or set to start automatically. A VPN can leave local connectivity intact while shifting web traffic or name resolution onto a different path.
IPv6 can also confuse the picture. Some networks only partly support it, and Windows may prefer it when it shouldn’t. If public IPv4 pings fail but the network still seems alive, compare the adapter’s IPv4 and IPv6 settings before you disable anything. Don’t turn IPv6 off as a permanent fix just because one guide suggests it. Use it only as a reversible test if you can turn it back on right away.
NRPT, the Name Resolution Policy Table, is the last Windows-only item worth checking if you use domain joins, VPNs, or managed DNS policies. NRPT can send only some names to special resolvers, which is why one app can fail while the rest of the PC looks normal. If this is a personal PC and you do not know that NRPT is in use, leave it alone until the simpler checks are done.
When to check the router, modem, or ISP instead
If public IPs also fail, stop treating it like a pure DNS issue. At that point, the question is whether the router still has a working WAN link, whether the modem is online, and whether other devices on the same network show the same failure.
Check whether a phone, tablet, or another computer on the same Wi-Fi can reach a public IP or browse normally. If they fail too, the Windows PC is probably not the real problem.
Then look at the router status page and WAN indicators. A router can answer local pings while its internet side is down, so the local network looks healthy even though the router has no working path upstream. If the WAN status shows disconnected, no IP, no DNS from the ISP, or a captive portal that never completes, the fix belongs on the router, modem, or ISP side.
If only one Windows PC is broken and other devices work, stay on the PC. If every device fails in the same way, the modem, router, or ISP line is the more likely fault. At that point, rebooting the PC again usually wastes time.
What to change first, then how to confirm it worked
Start with the least risky fix that matches the symptom. If public IPs work but names do not, renew the network settings before you reset anything broad. Microsoft says that ipconfig /renew is the right move for dynamically configured clients that need a fresh TCP/IP lease.
- Renew the adapter’s IP configuration.
ipconfig /renewIf that restores name resolution, the old lease or DNS settings were stale. If nothing changes, you still haven’t ruled out a bad DNS server or a Windows setting that overrides normal lookup.
- Clear only the DNS cache if names are still failing.
ipconfig /flushdnsFlushing DNS helps when Windows stored a bad answer. It does nothing for a dead WAN link, a bad DNS server, or a proxy problem. If the public IP ping already failed, flushing DNS is not the real fix.
- If the DNS server on the adapter is wrong, change it to a known-good resolver or back to DHCP, depending on your network policy. Keep the original setting written down so you can undo the change if it doesn’t help.
- If a proxy or VPN is present, disable it for a clean test. If the problem disappears, turn one item back on at a time so you can tell which one caused the break.
Verify the fix
Run the same three tests again and make sure all three behave normally. The router should ping, a public IP should ping, and nslookup should return a valid answer.
If you changed DNS, check ipconfig /all again and confirm the active adapter is using the server you expected. If you changed a proxy or VPN setting, confirm that browsers and other apps both work, not just one tab in one browser.
A clean result is when the PC reaches the router, reaches a public IP, and resolves a domain without delays or fallback behavior. If one of those still fails, the layer below it is still the place to look.
Conclusion
If the router ping works but the internet does not, use the three tests to pin down the broken layer before you change settings. Fix the matching cause, then verify with router ping, public IP ping, and `nslookup` again.
Frequently Asked Questions
Why can I ping my router but not google.com?
That usually means the local network is fine, but either DNS is broken or traffic beyond the router is not getting out. The deciding test is a public IP ping. If that fails too, look at routing, the router WAN, or the ISP. If it works, focus on DNS and Windows settings.
Does flushing DNS fix this every time?
No. `ipconfig /flushdns` only clears cached name answers on the PC. It can help when Windows stored a bad result, but it does nothing if the DNS server is wrong, the WAN is down, or a proxy or VPN is redirecting traffic.
How do I know whether Windows is using the wrong DNS server?
Run `ipconfig /all` and check the `DNS Servers` line on the active adapter, then confirm with `nslookup`. If the server listed there is stale, unreachable, or belongs to a VPN you are not using, that is likely the source of the failure.
Sources
- Troubleshooting DNS clients | Microsoft Learn (learn.microsoft.com)