Strange technical issue with my internet
General Tech Support
ResolvedHey guys, I’ve been having a weird issue with my laptop for a while now and I’ve tried everything to fix it, but nothing worked. I thought maybe one of you has dealt with this before.
The Problem: The internet is connected and the Wi-Fi is on, but whenever I try to search on Google or open any website, there’s no response at all. When I run the Troubleshooter, it says: "The DNS server isn't responding."
Solutions I’ve tried (that didn’t work):
Manually changed the DNS to (Google DNS 8.8.8.8) and (Cloudflare 1.1.1.1).
Performed a full Network Reset.
Used Command Prompt (CMD) as admin and ran (flushdns, release, renew, winsock reset).
Restarted both my laptop and the router multiple times.
The strange thing is, every time I think the problem is fixed and try to search for something on Google, it fails again even though it shows I'm connected. Any other ideas I could try? Could it be something with the router settings or the ISP itself?
The Problem: The internet is connected and the Wi-Fi is on, but whenever I try to search on Google or open any website, there’s no response at all. When I run the Troubleshooter, it says: "The DNS server isn't responding."
Solutions I’ve tried (that didn’t work):
Manually changed the DNS to (Google DNS 8.8.8.8) and (Cloudflare 1.1.1.1).
Performed a full Network Reset.
Used Command Prompt (CMD) as admin and ran (flushdns, release, renew, winsock reset).
Restarted both my laptop and the router multiple times.
The strange thing is, every time I think the problem is fixed and try to search for something on Google, it fails again even though it shows I'm connected. Any other ideas I could try? Could it be something with the router settings or the ISP itself?
Solution
@Leaf The issue was a DNS Resolution Failure caused by a conflict between VMware's virtual adapters and Hotspot Shield's leftover configurations. Even though the internet connection was alive (proven by tracert 1.1.1.1), the Windows Network Stack was unable to resolve domain names. I fixed it by performing a full network stack reset (winsock and int ip reset) and flushing the DNS cache, which cleared the corrupted routing caused by the virtual software
