Given that Ethernet can successfully ping both an IP (8.8.8.8) and a hostname (google.com), the Ethernet stack, DNS resolution, and basic connectivity are working. The issue is therefore not with the physical Ethernet hardware or basic IP configuration, but higher in the stack (Windows networking components, browser stack, security/filters, or OS corruption).
From the available guidance, the following Ethernet-focused troubleshooting steps are applicable:
- Verify Ethernet status in Windows
- Open Settings > Network & internet and check the Ethernet status.
- It should show Connected (Windows 11) or You're connected to the Internet (Windows 10). If it shows Action needed or similar, open the Ethernet details and review any error or proxy configuration.
- Run the Network troubleshooter
- Open Settings > Network & internet.
- Select Status (Windows 10) or the equivalent status view in Windows 11.
- Run Network troubleshooter and follow the prompts.
- This can detect misconfigurations between the OS and browser stack that are not obvious from ping tests.
- Run network stack reset commands
- Open Command Prompt as administrator.
- Run these commands in order:
-
netsh winsock reset
-
netsh int ip reset
-
ipconfig /release
-
ipconfig /renew
-
ipconfig /flushdns
- Restart the PC and test again over Ethernet.
- This resets Winsock and TCP/IP, which can fix cases where browsers fail while ping still works.
- Uninstall and reinstall the Ethernet adapter driver
- In Device Manager, expand Network adapters.
- Right-click the Ethernet adapter and select Uninstall device.
- Check Attempt to remove the driver for this device, then uninstall.
- Restart the PC; Windows will reinstall the driver.
- If Windows does not install it, install the vendor driver that was downloaded in advance.
- Use Network Reset as a last resort
- Open Settings > Network & internet.
- On Windows 11: Advanced network settings > Network reset.
- On Windows 10: Status > Network reset.
- Select Reset now, confirm, and let the PC restart.
- This removes and reinstalls all network adapters and resets all network settings to defaults, which can resolve OS-level corruption affecting browsers but not basic ping.
- Compare behavior via Wi‑Fi vs Ethernet
- Since Wi‑Fi works, use it as a baseline.
- After each Ethernet change (driver reinstall, network reset, Winsock reset), test the same sites and browsers over Ethernet and confirm whether behavior now matches Wi‑Fi.
If Ethernet continues to ping successfully but browsers fail only when using Ethernet and not Wi‑Fi, and all of the above OS/network stack resets have been performed, that strongly suggests a deeper OS or driver interaction issue rather than a simple hardware fault on the NIC. In such a case, an in-place repair of Windows or a clean OS reinstall on that hardware would be the next supported step before concluding the motherboard is defective.
References: