Windows issues where connection exists but no internet access, yet USB tethering functions properly
Windows issues where connection exists but no internet access, yet USB tethering functions properly
Hey there, I've been experiencing Ethernet issues with my PC over the last couple of months. It seems to work sometimes and not others, especially when using a USB tether for my phone. In Windows 11 settings it says connected but no internet, but my phone works fine. Other devices have internet access, so it looks like the problem is specific to my PC. When I go to Troubleshooting settings, I see an error about the DHCP server not found. I just ran a network reset and wondered if that's a Windows issue. Could you help me figure this out? Any extra details would be great. Thanks!
Have you attempted a network reset before? If not, look up "Network Reset" in the Windows search bar and open it. This should resolve the issue if any network configuration is incorrect.
It seems there are some unusual points here. One of your Ethernet adapters appears to be active but isn’t getting an IP address—it displays a local address like 169.254.112.27, which is a Windows internal IP and not suitable for internet access. It’s possible Windows is attempting to route traffic through this adapter. The second adapter’s gateway is listed as 192.168.11.3, but usually gateways end with xxx.xxx.xxx.1. I recommend turning off the first Ethernet adapter in your Windows settings and checking if the second adapter shows the same gateway address and subnet mask as another device. This can help confirm whether the issue lies with the adapter configuration or routing.
Wow! Looks like you're using your phone for internet access. You plan to extract it and capture a screenshot of the command prompt!
Yes, the first adapter is the Ethernet one linked straight to your router. Make sure the cable is securely inserted. Are the orange or green indicators on the Ethernet port lighting up? If they are, check the connection path and destination device.
The system reported an unusual issue indicating no network was recognized.