Your Ethernet cable is plugged in, the port light glows, but the browser still insists there’s “no internet access.” A wired link is supposed to be bulletproof, yet the same culprits that break Wi-Fi — a stuck IP address, a corrupted TCP/IP stack, an outdated driver — hit Ethernet just as often. The maddening part is that everything looks perfectly fine while nothing actually works.
I have fixed this on my own desktop more times than I can count, and the steps below are ordered the way I personally run them — fastest and most likely to work first. Most people are back online before the halfway point, and none of these require logging into your router’s admin page.
Quick Answer
Re-seat the Ethernet cable, then run ipconfig /release and ipconfig /renew in an elevated Command Prompt. Still offline? Run netsh int ip reset and netsh winsock reset, then restart. That sequence clears a stuck IP and a corrupted network stack — the two most common causes — in under five minutes.
Is the cable or port actually the problem?
Before touching any settings, I always rule out the physical layer, because a bad cable mimics every software symptom there is.
- Unplug the cable from both ends and firmly re-seat it. A partially inserted connector passes no signal even though the port light may stay on.
- Check the port light on your router or switch. Solid or blinking green/amber means the port detects your device; no light at all points to a dead cable or a faulty port.
- Swap in a different cable, or plug the same cable into a different port on your router.
- Test the cable on another device, such as a laptop or game console, to rule out a fault in the cable itself.
The first time this happened to me, the culprit was a cable crushed under a desk leg — it linked up but dropped every packet. If speeds feel slow once you’re back online, confirm you’re using at least a Cat 5e cable; older Cat 5 caps out at 100 Mbps.
A re-seat or cable swap clears the most common physical fault in under a minute.
How do I release and renew a stuck IP address?
A “stuck” IP — especially one starting with 169.254.x.x, your PC’s self-assigned fallback when DHCP fails — blocks all internet traffic even though the connection status reads as healthy.
- Press Windows + R, type
cmd, then press Ctrl + Shift + Enter to open an elevated Command Prompt. - Run
ipconfig /releasefirst, so you don’t re-acquire the same broken lease. - Run
ipconfig /renew. - Open a browser and test. If
ipconfigstill shows a 169.254.x.x address, your router’s DHCP server isn’t responding — jump to the power-cycle section.
Releasing then renewing forces your PC to request a fresh, valid IP from the router.
Why does resetting TCP/IP and Winsock fix it?
Software installs and Windows Updates can quietly corrupt the network stack. Three commands rebuild it without touching any of your personal data.
- In the elevated Command Prompt, run these three lines in order:
netsh int ip reset netsh winsock reset ipconfig /flushdns
- Restart your PC and test the connection.
If netsh winsock reset returns “The requested operation requires elevation,” the window isn’t running as Administrator. Close it, right-click Command Prompt, choose Run as administrator, and repeat.
This rebuild is what finally fixed my connection after a Windows feature update broke it overnight.
Could an Ethernet driver be the culprit?
Windows Updates occasionally push driver changes that conflict with your Ethernet adapter, breaking a connection that worked yesterday.
- Right-click Start and open Device Manager.
- Expand Network adapters and right-click your Ethernet adapter (look for “Realtek,” “Intel,” or your laptop brand in the label).
- Choose Update driver, then Search automatically for drivers.
- If Windows finds nothing, visit your adapter maker’s support page — Realtek, Intel, Dell, Lenovo, or HP — and download the latest driver manually.
- For a clean reinstall: right-click the adapter, choose Uninstall device, tick Delete the driver software, confirm, and restart. Windows reinstalls a fresh copy on reboot.
Updating or reinstalling the wired adapter driver clears conflicts that survive every other fix.
What if I can ping but websites won’t load?
If ping 8.8.8.8 returns replies but pages still won’t open, your DNS resolver is the bottleneck — not the Ethernet link itself. Switching to a public DNS server fixes this immediately.
| DNS provider | Primary | Secondary | Best for |
|---|---|---|---|
| 8.8.8.8 | 8.8.4.4 | Speed and reliability | |
| Cloudflare | 1.1.1.1 | 1.0.0.1 | Privacy plus speed |
| OpenDNS | 208.67.222.222 | 208.67.220.220 | Family content filtering |
- Open Settings, then Network & Internet, then Ethernet, and click your connection name.
- Under DNS server assignment, select Edit, then Manual.
- Enter your preferred primary and secondary addresses, then click Save.
If you want this set up across every gadget you own, my walkthrough on changing your DNS server on any device covers it step by step. If the failure shows as a named error instead of a blank page, see fixing “DNS server not responding” on Windows.
A public DNS resolver loads websites when the ISP’s default resolver stalls.
How do I power-cycle the modem and router correctly?
A router holding a stale WAN lease blocks every device on your network, wired and wireless alike. The order of the restart matters more than most people realise.
- Unplug your modem (the box your ISP provided) first.
- Unplug your router second.
- Wait 60 seconds to flush cached data.
- Plug the modem back in and wait for the sync lights to settle, typically 30 to 60 seconds.
- Plug the router back in and wait another 30 seconds.
- Test your Ethernet connection.
If every device is still offline after a full power-cycle, the fault is upstream. The U.S. FCC broadband speed guide is a useful reference before you call your ISP, since it helps you describe what speed you’re actually paying for.
Powering the modem up before the router lets your network pull a fresh, valid WAN lease.
Common Mistakes to Avoid
- Restarting the router before the modem. The router grabs a stale WAN address. Fix: go modem off, router off, modem on, router on, in that order.
- Skipping the cable swap. A visually intact cable with a damaged internal pin causes intermittent drops that look like a software problem. Fix: try a different cable before running any commands.
- Ignoring a 169.254.x.x address. That IP means DHCP failed, not that the cable is bad. Fix: restart the router, then run
ipconfig /renew. - Running
/renewwithout/releasefirst. You risk re-acquiring the same broken lease. Always release before you renew. - Updating the wrong adapter in Device Manager. Wi-Fi and Ethernet adapters list with similar names. Fix: confirm you’re right-clicking the wired Ethernet adapter, not the wireless one.
Frequently Asked Questions
Why does my Ethernet say “Connected” but there’s no internet?
“Connected” only confirms your PC can talk to the router, not that the router has a live internet feed or handed you a valid IP. Run ipconfig: a 169.254.x.x address means DHCP failed, while a normal 192.168.x.x address points to DNS or your ISP. When this hit me, the address was 169.254 and a router restart cleared it instantly. If you see the same symptom over Wi-Fi, my guide on Wi-Fi connected but no internet covers the wireless version.
Can a damaged cable cause no internet while the port light stays on?
Yes. A damaged cable can hold just enough electrical signal to light the link LED while dropping the throughput real traffic needs. I once chased a “software” outage for an hour before a spare cable fixed it in 30 seconds, so swap the cable before you touch any settings.
Do these fixes work on a Mac?
Partially. On macOS, renew the lease under System Settings, then Network, then Ethernet, then Details, then Renew DHCP Lease, and set DNS under the DNS tab. To clear the DNS cache, I open Terminal and run sudo killall -HUP mDNSResponder. There’s no direct Winsock equivalent, but a full reboot achieves a similar reset.
How do I tell whether the problem is my router or my ISP?
Connect your PC straight to the modem with an Ethernet cable, bypassing the router. If the internet works, your router is the problem; if you’re still offline, the fault is the modem or your ISP’s line. I keep a short cable on hand just to run this one test quickly.
Is it safe to use 1.1.1.1 as my DNS server?
Yes. Cloudflare’s 1.1.1.1 is a free public resolver that needs no account, and I’ve run it on my own machines for years. You can switch back to automatic, ISP-assigned DNS at any time from the same network settings panel, so there’s no lock-in.
Conclusion
Nearly every “Ethernet connected, no internet” case traces back to a stuck IP, a corrupted network stack, or a driver conflict — all fixable in minutes with tools already on your PC. Work through these steps in order and you’ll likely be back online before a support agent picks up. If speeds recover but still feel sluggish, read my guide on speeding up a slow internet connection next.