If Ethernet says connected but websites will not load, check DNS, gateway, IP assignment, proxy, VPN, firewall, browser DNS settings, router LAN state and ISP routing.
Start by comparing what still works: browser versus app, Wi-Fi versus mobile data, Ethernet link versus DNS, or restart versus smaller network refresh. That comparison tells you where the fix belongs.
Start with the exact layer that still works
Ethernet connected but websites will not load usually means the physical cable link is only part of the story. The computer can see the router, the router port light may blink and Windows may show connected, but website names still fail, pages hang or apps report no internet. The most common causes are DNS failure, missing gateway, stale IP lease, proxy settings, VPN routes, firewall rules or a router LAN service that is stuck. It is not always a bad cable, though a cable test is still quick.
The fix is to check whether the computer has a valid IP, gateway and DNS, then test whether the problem is name lookup or all traffic. If IP addresses respond but websites do not, DNS is the target. If nothing outside the router responds, look at gateway, DHCP, VPN or router handoff. This keeps the troubleshooting clean instead of randomly swapping parts.
Quick diagnosis table
Try these fixes in order
Use this order so you prove the failure point before changing broad settings.
- 01
Check IP, gateway and DNS
Open network details and confirm the computer has a normal local IP, default gateway and DNS servers. Missing gateway means connected is only physical.
- 02
Test another browser and app
If one browser fails, browser DNS or proxy may be the issue. If every app fails, the system network path is the issue.
- 03
Flush DNS and renew IP
Clear DNS cache, release and renew the IP address, then test the same site again.
- 04
Try a known DNS resolver
If names fail but the connection is otherwise alive, test a reliable public DNS resolver.
- 05
Check proxy settings
A stale proxy can make websites hang even when Ethernet is connected. Turn off unknown proxy settings.
- 06
Disable VPN kill switch for a test
VPN clients can leave routes behind. Turn VPN off completely and test Ethernet again.
- 07
Swap cable and router port
If only Ethernet fails and Wi-Fi works, try a different cable and LAN port. This checks the physical layer without guessing.
- 08
Restart router if multiple wired devices fail
If more than one Ethernet device has the same symptom, the router LAN/DHCP/DNS service may be stuck.
- 09
Retest after a restart or reconnect
After the fix appears to work, restart the app, reconnect the adapter or reboot the device once. A fix that survives the next restart is much more reliable than one lucky successful load.
Detailed checks
The cable link is only layer one
Ethernet connected means the computer detected a physical or local link. It does not prove DNS, gateway and routing are healthy.
- That is why network details matter more than the icon.
DNS failure feels like total internet failure
Most people open websites by name. If DNS fails, the internet appears dead even when the route is partly working.
- Testing DNS separates name failure from full connection failure.
Proxy and VPN issues can affect only this PC
Proxy and VPN settings live on the computer, so other devices can work while this Ethernet connection fails.
- That is a strong clue to avoid router resets.
The repeat pattern matters
If Ethernet fails after VPN, after sleep or after moving ports, the trigger tells you where to look.
- Write down the trigger before applying broad resets.
Why repeat testing matters
A single successful load can be a cached page, a lucky route or a temporary service recovery. Repeat testing shows whether the fix changed the actual broken layer.
- Use the exact same app, website or connection state that failed before. That keeps the confirmation honest.
Mistakes to avoid
Do not assume one working browser proves every app has clean internet.
Do not blame the router when the pattern follows one device, app, VPN or adapter.
Do not change DNS, VPN, firewall and drivers all at once. Test one layer at a time.
FAQ
Why does Ethernet say connected but websites won't load?
Because the cable link can be active while DNS, gateway, proxy or routing is broken.
Check IP details instead of trusting the connected label.
Is the Ethernet cable bad?
It can be, especially if the link drops or only one port fails.
But if the link stays connected and names fail, DNS or gateway is more likely.
Can DNS cause websites not to load?
Yes. DNS failure is one of the most common causes of this symptom.
Try another DNS resolver and flush DNS cache.
Can VPN cause this?
Yes. VPN routes or kill switches can block traffic after disconnecting.
Disable VPN fully and test again.
Should I restart the router?
Restart it if multiple devices fail or the gateway/DHCP looks wrong.
If only one PC fails, check PC settings first.
Why does Wi-Fi work but Ethernet does not?
That points to Ethernet adapter, cable, LAN port or Ethernet-specific settings.
Compare IP settings between Wi-Fi and Ethernet.
Can proxy settings break websites?
Yes. A stale proxy can stop browsers and apps from reaching websites.
Turn off unknown proxy settings and test.
What if IP addresses work but domains do not?
That is a classic DNS clue.
Change DNS or fix the DNS server configured on the router or PC.
When should I call the ISP?
Call if multiple devices fail, modem/router status is bad or direct modem testing also fails.
If only one computer fails, solve the local settings first.
Outside references
- Microsoft Windows Support
Official Windows network troubleshooting reference.
- Cloudflare DNS Help
Reference for testing a known public DNS resolver.