Windows can show a Wi-Fi connection even when websites fail to open. Start with two quick comparisons, then check whether the problem is local to your PC, affects the network, or appears only when looking up website names.
1. Check another device and another site
Try two unrelated sites. If both fail, test another device on the same Wi-Fi, with mobile data temporarily off so it cannot hide a Wi-Fi failure. If both devices fail, check whether the network requires a sign-in page or whether there is an outage. On a managed network, contact the network administrator. If only the Windows PC is affected, continue below.
2. Find the default gateway
Open Command Prompt and run:
ipconfigFind the active Wi-Fi adapter and its default gateway. If it lists an IPv4 gateway, you can try pinging that actual address. For example, if Windows lists 192.168.1.1, run:
ping 192.168.1.1A reply shows that the gateway answered. A timeout is inconclusive because some devices block ping. If the adapter shows no gateway and other devices work, reconnect to Wi-Fi and run the check again. Microsoft ipconfig reference.
3. Check name resolution
nslookup example.comAn address in the answer shows that this lookup succeeded. Repeated timeouts on several known domains can point to a DNS or connectivity issue. If lookups succeed but only one browser fails, compare another browser and report any VPN, proxy or browser-specific symptoms to support. A successful lookup alone says nothing about whether a particular web page can load. Microsoft nslookup reference.
What to report
Record which devices and sites failed, whether a gateway was listed, and what the lookup returned. For example, “My phone could browse on the same Wi-Fi, but the laptop had a gateway and lookups timed out.” This gives support a starting point before any network reset. Microsoft Windows Wi-Fi troubleshooting.
Related: what to consider when setting up a wireless network.
Posts
0 Comments