Ethernet Not Working in Windows 11? A Wired PC With No Connection — Here's the Fix

You plugged an Ethernet cable straight from your router into your PC — the connection that's supposed to be the rock-solid one — and you've got nothing. Maybe Windows says "Not connected," maybe it shows the little globe with "No internet," or maybe you get the specific error "Ethernet doesn't have a valid IP configuration." It's especially maddening on a desktop that has no Wi-Fi to fall back on: the cable is the only way online, and it's dead.

Here's the thing that makes a wired problem different from — and easier than — a Wi-Fi one: it's physical. There is an actual cable and an actual socket, which means you can literally see where the break is before you change a single setting. Most of these turn out to be the cable, the port, or one switch inside Windows, and the whole thing is usually a five-minute fix once you know the order to work in.

One quick check that this is the right guide first. This is for a computer connected by an Ethernet cable. If you're on Wi-Fi — full bars but nothing loads, or a laptop that won't join the network at all — those have their own fix lists, linked at the bottom. If your network adapter has vanished from Device Manager entirely, or the machine is dead on both a cable and Wi-Fi, that's usually a corrupted network driver (also linked below). And if every device in the house is offline, it's your modem or provider, not this PC — we'll come back to that. Otherwise, read on.

Start at the port lights — they tell you where the break is

Before anything else, look at the Ethernet socket itself, where the cable plugs in — on the back of the PC and on the router. Almost every Ethernet port has one or two tiny LEDs built into it, and they are the single most useful diagnostic you own. One is the link light: when it's solid, the two ends have found each other electrically — the cable is good, both ports are on, and they've agreed on a connection. The other blinks with activity as data actually moves. This is a free hardware test that Windows can't fake.

That gives you a clean fork. If there is no light at all on the port — dark on the PC side, or dark on the router side — the problem is physical: the cable, the socket, the wall jack, or the adapter hardware. Nothing in Windows will fix a dead cable, so don't waste an hour in Settings; work the "no lights" section below. If the link light is solid (and especially if the activity light flickers) but you still have no internet, the physical link is fine — the break has moved up into the address, the driver, or your provider, so skip to the "lights on but no internet" section. Knowing which half you're in saves you from chasing the wrong fix.

No lights: work the cable and the port

A dark port means the connection was never physically made, so this is all hands-on and none of it costs anything. Start by reseating the cable — unplug it at both ends and push it firmly back in until the little clip clicks. A cable that looks plugged in but isn't quite latched is the most common cause of a dead port, and reseating it is the fix more often than anything else.

If that doesn't bring the light on, swap the cable for a different one you know works — pull the cable from a device that's definitely online and try it. Ethernet cables fail silently: a kink, a crushed spot where a chair rolled over it, or a broken locking tab (the small plastic clip on the plug) that lets the plug wiggle loose can all kill the link with no outward sign. While you're at it, look at the plug's clip — if it's snapped off, the plug won't seat properly and needs re-ending or replacing.

Then move the cable to a different port on the router or switch, in case that one jack has died, and if you're plugging into a wall jack, test by running a cable straight from the router instead — a wall jack relies on in-wall wiring that may never have been connected. To isolate whether it's the cable or the computer, plug that same cable and port into a second device: if the other device lights up and gets online, the fault is your PC's port; if it stays dark too, it's the cable or the jack. One more on cables: for a full gigabit (1000 Mbps) connection you want at least Cat5e or Cat6 — a very old Cat5 cable or a damaged one can drop you to a crawling 100 Mbps or fail to link at all, so a mystery-slow or flaky wired connection is sometimes just a tired cable.

Lights on but no internet: the Windows side

If the port light is solid but you're still stuck, the cable did its job and the problem is inside the computer. Work these in order. First, make sure the adapter isn't simply switched off: press Windows key + R, type ncpa.cpl and press Enter. Find your Ethernet connection — if it's greyed out and says "Disabled," right-click it and choose Enable. This is a genuinely common one, because it's easy to disable an adapter by accident or have a cleanup tool switch it off, and on a wired-only desktop it takes you completely offline. If the same window shows "Network cable unplugged" while a cable is clearly plugged in, that points back to a bad cable, port, or the adapter itself — back to the previous section.

The signature wired error is "Ethernet doesn't have a valid IP configuration," often paired with an "Unidentified network" label or an address that starts with 169.254 (you can see it by typing ipconfig in a Command Prompt and reading the IPv4 line). All three mean the same thing: the router never handed your PC a real address, so it gave up and assigned itself a placeholder. Fix it by forcing a fresh request — open Command Prompt as administrator (Start, type cmd, right-click, "Run as administrator") and run ipconfig /release, then ipconfig /renew. If it comes right back, reset the networking plumbing with netsh int ip reset and netsh winsock reset, then restart. (That reset sequence is the same workhorse fix a stuck Wi-Fi connection needs, and we walk through it step by step in the "Wi-Fi connected but no internet" guide linked below.)

Two more wired-specific culprits are worth a look. In that same ncpa.cpl window, right-click your Ethernet adapter, choose Properties, open "Internet Protocol Version 4 (TCP/IPv4)," and confirm both "Obtain an IP address automatically" and "Obtain DNS server address automatically" are selected — a leftover manual (static) address from an old setup will let the link come up but never reach the internet. And try turning off Fast Startup (Control Panel > Power Options > "Choose what the power buttons do" > uncheck "Turn on fast startup"), then do a full shutdown and cold boot: Fast Startup is a known cause of the "no valid IP configuration" error because it can leave the network adapter in a half-asleep state. If the link is up but only some things work — most sites fail, or a program can't reach the internet while others can — a VPN, a stray proxy setting, or a slow DNS server is usually the reason; those checks are identical to the Wi-Fi case and are covered in that same linked guide, so we won't repeat them here.

When it's the driver — or the whole house

If none of that lands, the trail forks two ways. Open Device Manager (right-click Start > Device Manager) and expand "Network adapters." If your Ethernet adapter has a yellow warning triangle, or it's missing entirely, or the machine is equally dead on Wi-Fi, you've crossed from a settings problem into a corrupted or missing driver. The cure is to reinstall the network driver — which is a catch-22 on a machine that can't get online, so you grab the right driver on a phone or another PC and move it over by USB. That's its own job, and we cover it in detail in our guide on a corrupted network driver knocking a computer offline.

The other fork is that it isn't your PC at all. If every device in the house is offline, walk to your modem and router and read the light labeled "Internet," "Online," or "WAN": if it's off, red, or blinking amber, the outage is between the box and your provider. Power-cycle properly — unplug both the modem and router, wait thirty seconds, plug the modem back in first and let its Online light go solid before you plug the router back in — and check your provider's app for an area outage. There's nothing to fix on your computer when the whole network is down; we cover that side in the "Wi-Fi connected but no internet" guide too.

Where we come in

A dead wired connection is one of the more satisfying problems to fix because it almost always resolves to something concrete: a cable that isn't quite clicked in, a jack that was never wired, an adapter switched off, or an address the router never handed out. Reading the port lights first tells you which of those you're dealing with in about ten seconds, and from there the list above catches the large majority — with no software to buy and no "network booster" cable or dongle to order.

If you've worked through it and the port is still dark or the address still won't come, that can point to a failed adapter, a driver that needs a proper reinstall, or wiring in the wall that needs tracing — the kind of thing that's quicker to hand off than to fight. We help homes and small businesses across Southern California and the Coachella Valley get wired connections working every day: we'll find out whether it's the cable, the port, the PC, or the provider, do the driver reinstall onsite when it's needed, and — because we don't sell hardware — tell you honestly whether you need a new cable, a new network card, or nothing at all.