I'm helping a neighbour resolve an issue with the wireless connection between their primary desktop PC and their router, and as such, I have limited time to access the PC.
The main issue is that the desktop PC can search for and connect to the router wirelessly, however the connection status is "Limited" and cannot access any websites. PC and router were working as expected previously.
The desktop PC has a wireless card which connects to the wireless router via a wireless range extender.
My first step was to run the built in "Windows Network Diagnostics". There were two different messages that I received throughout my testing.
1) The DNS server isn't responding
2) Investigate router or broadband modem issues
Next I unplugged the router, turning it off and on again. This had no impact.
I then started testing using known goods.
1) Both a laptop and a phone were able to connect to the router
2) The desktop PC was able to connect to my android phone when acting as a hotspot using mobile data
3) The desktop PC was able to connect to my android phone when acting as a hotspot using WiFi sharing (connected to the same router)
4) Unfortunately, I did not have access to an ethernet cable long enough to test whether the desktop PC could establish a wired connection with the router
From this, I came to the conclusion that it does not seem to be a hardware issue.
I then accessed the router configuration (192.168.0.1) from a laptop.
1) I tried changing the WiFi channel. No effect.
2) I checked the list of connected devices. The desktop PC was not listed, and there were two instances of "UNKNOWN" devices connected to the router.
I started using cmd to test.
1) I tried pinging the Google DNS server (126.96.36.199). Request timed out.
2) I tried pinging the router. Request timed out.
3) I ran ipconfig /all. Nothing seemed obviously wrong when compared against the same command run for the working laptop (however this isn't one of my strengths, so this is mainly an assumption). The PC has an IP address ending in x.x.x.100
I attempted to manually set an IP address and DNS server (Google's public DNS 188.8.131.52 / 184.108.40.206). No effect. Changed back to automatic.
Finally, in an act of near desperation, I ran netsh winsock reset catalog and restarted the computer. Still no effect.
I'm at a loss. Any thoughts?
Edited by TheWildCard, 22 May 2018 - 05:37 AM.