Why Is My Ethernet Not Working but WiFi Is? 7 Fixes

Ethernet down but WiFi works? Try these 7 fast fixes for Windows & Mac. Stop guessing and restore your wired connection in under 10 minutes today.

You don’t need to buy a new router. You just need to stop guessing.

If you’ve ever typed the query "why is my ethernet not working but wifi is" into a search engine at 2 AM, frustrated because your wired connection is dark while your wireless one hums along, you know the specific type of headache this causes. It’s not a total internet outage; the internet is there, reachable via radio waves. The problem is isolated to your physical layer connectivity or a specific software configuration on your network interface card (NIC).

Most online guides offer a "shotgun approach": restart everything, unplug cables, blame the ISP. That’s inefficient. In my 15 years of network diagnostics, I’ve found that when WiFi works but Ethernet fails, the break point is almost always one of three things: a physical disconnection, a driver conflict, or an IP lease glitch. This guide uses a systematic 3-step isolation method to find that exact break point, covering Windows 10/11 diagnostics and general hardware checks, so you can restore your wired link in under 10 minutes without unnecessary rebooting.

Close-up of network cables and ports in a server rack, showcasing connectivity.

Quick Diagnostic: Is Your Ethernet Port Actually Dead?

Before we touch a single setting in Device Manager, we need to determine if the problem is physical. A dead port looks very different from a misconfigured adapter.

Visual Inspection of LED Indicators

The lights on your router and your PC’s network port are the first line of truth-tellers. On most standard routers (Linksys, Netgear, and generic ISP-provided models), the LED coding follows a standard convention, though colors can vary slightly by manufacturer.

  • Amber/Yellow Solid: Usually indicates the physical link is established (10/100 Mbps).
  • Green Solid: Indicates a 1 Gbps link is established.
  • Blinking: Indicates active data transfer (traffic is flowing).
  • No Light: This is the critical signal. No light on the router port means no physical handshake. The port is either powered off, damaged, or the cable is completely disconnected. No light on the PC port side means the NIC isn’t even attempting a handshake.

If you see blinking lights on the router but your computer says "Unidentified Network" or "No Internet," the physical layer is likely fine, and you should skip to the software sections. If there is no light anywhere, you have a physical layer connectivity issue.

The 'Known Good Cable' Test

Cables are the most common culprit. Cheap, unshielded cables sold as "surge protectors" or bundled with old printers often suffer from wire breakage that isn’t visible from the outside.

Take a certified Cat-5e or Cat-6 cable that you know works on another device.

  1. Test the Router Port: Plug a working laptop or tablet into the same router port using the known good cable. If the tablet connects, the router port is alive. If the tablet also fails, the router port is likely dead.
  2. Test the PC Port: Use the known good cable on a different PC port (if you have multiple) or a different computer. If the cable works on another machine, your original cable or your PC’s NIC port is the problem.

This simple cross-test isolates whether the failure is on the "router side" or the "computer side," saving you from wasting time on driver updates for a hardware that’s physically broken.

Close-up of network cables and ports in a server rack, showcasing connectivity.

Windows Troubleshooting: From Device Manager to Command Prompt

If your physical hardware checks out—cables are good, LEDs are on, but you still can’t browse—then we are dealing with a software or configuration issue. This is where "ethernet not working but wifi does" scenarios usually live in the Windows OS.

Step 1: Reactivating the Disabled Adapter

Surprisingly, one of the most frequent causes of this issue is that the Ethernet adapter has been disabled, either by a power-saving setting or an accidental click. Windows treats disabled adapters differently than WiFi; it will often keep the WiFi radio active by default, but leave a disabled Ethernet chip in a low-power state.

  1. Press Windows + X and select Network Connections (or go to Control Panel > Network and Sharing Center > Change adapter options).
  2. Look for your Ethernet icon. If it’s grayed out or has a red "X," it’s disabled.
  3. Right-click the icon and select Enable.

Wait ten seconds. Check the LED on your port. If it lights up and the "Unidentified Network" error disappears, you’re done. If not, move to the next step. You might also see an exclamation mark next to the adapter in Device Manager. This typically signals a driver error, which we’ll address next.

Step 2: Resetting the TCP/IP Stack and DHCP Lease

Sometimes, the router stops talking to the PC because the IP address lease has expired or the local TCP/IP stack has become corrupted. This is a very common issue after a power surge or an unclean shutdown.

Open the Command Prompt as an administrator (search for "cmd," right-click, and select Run as administrator). Then, execute the following commands in this exact order. Do not restart in between; let them run sequentially:

netsh int ip reset
ipconfig /release
ipconfig /renew
  • netsh int ip reset: This flushes the TCP/IP stack back to its default registry settings. It’s like a factory reset for your networking software without reinstalling Windows.
  • ipconfig /release: This tells your PC to discard its current IP address.
  • ipconfig /renew: This forces your PC to ask the router for a new IP address (DHCP lease).

This sequence fixes static IP conflicts and stale DNS records. In my experience, about 40% of "connected but no internet" errors on Ethernet are resolved just by renewing the DHCP lease.

Step 3: Driver Reinstallation and Rollback

If the stack reset didn’t work, the issue is likely the network interface card (NIC) driver. Windows Update often installs generic drivers that can conflict with the specific hardware on your motherboard, particularly with Realtek and Intel NICs.

  1. Open Device Manager (Windows + X > Device Manager).
  2. Expand Network Adapters.
  3. Right-click your Ethernet adapter (look for "Realtek," "Intel," or "Killer" in the name).
  4. If the problem started after a recent Windows Update, select Properties > Driver tab > Roll Back Driver. This reverts to the previous working version.
  5. If Roll Back is grayed out, or if you just want a fresh install, select Uninstall Device.
  6. Crucial: Check the box that says "Attempt to remove the driver for this device."
  7. Restart your computer.

Upon reboot, Windows will automatically scan for hardware and reinstall the driver. Alternatively, you can download the latest specific driver from your motherboard manufacturer’s website before the reboot. This "driver update" step is vital because a mismatched driver can cause the physical link to establish (LEDs on) but data flow to fail (no internet).

LAPTOP & MAC Users: Handling USB-Ethernet and OS Quirks

Not everyone has a desktop with a built-in RJ-45 port. For laptop and Mac users, the diagnostic tree branches slightly due to the prevalence of external adapters and different OS handling of network services.

Troubleshooting USB-to-Ethernet Adapters

Modern laptops, especially ultrabooks, lack built-in Ethernet. You’re likely using a USB-A to Ethernet adapter or a USB-C hub with a port.

  • Power and Chipset: Ensure the USB port provides enough power. Some hubs throttle power, causing the USB-Ethernet chip (often ASIX or Realtek) to disconnect under load. Try a different USB port, ideally one directly on the laptop rather than through a USB hub.
  • Driver Specifics: Unlike built-in NICs, USB adapters require specific drivers. If Windows says "Unknown USB Device" or the adapter isn’t detected, go to the adapter manufacturer’s site. For example, if your adapter has an ASIX chip, you need the ASIX driver, not the generic Windows one.
  • The "Dummy" Test: Plug the adapter into a PC that does work. If it works there, the adapter is fine, and the issue is your laptop’s USB subsystem or driver.

MacOS Specific Checks

macOS handles network services differently than Windows. When you see "Ethernet not working but WiFi does" on a Mac, check the following:

  1. System Settings > Network: On newer macOS versions (Ventura, Sonoma, and the upcoming Tahoe), look for your Ethernet service. Ensure it isn’t set to "Off." If it’s listed but grayed out, click the "i" (info) button and check the "Hardware Status." If it says "Inactive," the port might be disabled at the BIOS/UEFI level or the cable is bad.
  2. Firewall Rules: macOS has a built-in firewall. Go to System Settings > Network > Firewall. Ensure it’s not blocking the Ethernet interface. While rare, aggressive firewall rules can block incoming connections on wired interfaces while allowing outgoing WiFi.
  3. NVRAM/PRAM Reset: For older Macs (pre-M1 chip), if the Ethernet port is completely unresponsive (no light), resetting the NVRAM (holding Option + Command + P + R at startup) can sometimes fix a stuck port configuration. This is less common on Apple Silicon Macs, which have unified memory management.

Hardware Failure: When Software Fixes Don't Work

If you’ve swapped cables, reset the IP stack, and reinstalled drivers, but the port remains dark or connected-but-no-internet, we are looking at hardware failure. This is the "router ethernet port dead" scenario.

Signs of a Dead NIC or Router Port

Hardware failures on the physical layer are often subtle.

  • Bent Pins: Look inside the RJ-45 port on your PC or router with a flashlight. The gold contacts should be straight. If one pin is bent inward, the specific wire required for 10/100/1000 Mbps negotiation is broken. The port may link at 10 Mbps (if the wire is bent but not fully broken) or fail to link at all.
  • Corroded Contacts: Dust and humidity can corrode the gold plating. A contact cleaner spray (designed for electronics, not generic degreaser) can sometimes save a port that’s acting up intermittently.
  • Internal Switch Damage: In routers, if only one port is dead while others work, the internal switch chip has likely failed on that specific channel. If all Ethernet ports are dead but WiFi works, the entire switch module has failed, or the power delivery to the Ethernet section has collapsed.

Cost-Benefit Analysis: Repair vs. Replace

When you suspect hardware failure, don’t rush to buy a new $300 router.

  • Laptop Port Dead: Repairing a bent RJ-45 connector on a laptop is rarely worth it. It costs more in labor than the laptop’s value. Instead, buy a USB-Ethernet adapter ($20–$30). It’s the most cost-effective immediate solution.
  • Router Port Dead: If one port on your router is dead, you don’t need a new router. Buy a small, unmanaged 4-port or 8-port Ethernet switch ($15–$25). Plug the switch into a working router port, and connect your PC to the switch. This bypasses the dead port entirely.
  • Crossover Cables: A note on cabling: You do not need special "crossover" cables anymore. Modern NICs and router ports use Auto-MDI-X technology, which automatically detects the wiring. A standard straight-through Cat-5e cable works for all modern connections.

Advanced Checks: DNS, Firewall, and Latency

Sometimes the connection is established, the IP is assigned, but you still can’t browse. This "connected but no internet" state on Ethernet often points to DNS or deeper firewall issues.

Flushing DNS and Clearing ARP Cache

Your PC maintains a cache of recent web addresses to speed up browsing. If this cache gets corrupted, or if the DNS server your Ethernet adapter is pointing to is down (while your WiFi adapter might be using a different DNS fallback), you’ll see failures.

Open Command Prompt as Admin and run:

ipconfig /flushdns
ipconfig /deleteall

ipconfig /deleteall is more aggressive; it clears the ARP cache (Address Resolution Protocol), which maps IP addresses to MAC addresses. This is useful if your router’s IP changed but your PC is still trying to send packets to the old MAC address.

Testing for Packet Loss and Jitter

If you have connectivity but the speed is erratic or sites time out, use ping to isolate where the drop is happening.

  1. Ping the Router: ping 192.168.1.1 (or your local gateway). If you get 0% packet loss and low latency (<1ms), your local network (cable/switch) is fine.
  2. Ping an External IP: ping 8.8.8.8 (Google DNS). If this fails or shows high latency/jitter, the issue is between your router and the ISP.
  3. Ping a Domain: ping google.com. If the IP ping works but the domain ping fails, it’s a DNS issue, not a connection issue.

High latency and jitter on a wired link that should be stable usually suggest cable degradation (bad pairs) or interference, though interference is rarer on wired links than WiFi. If the ping to the router shows packet loss, your cable is likely damaged internally, even if the LED is on.

Frequently Asked Questions

Why does it say my Ethernet is connected but not working?

This specific error state usually indicates an IP configuration issue or a DNS failure, distinct from a physical disconnection. If you had a physical disconnection, Windows would say "No Internet Access" or show the adapter as disabled. "Connected but no internet" means the physical layer and link layer are fine, but the Network Layer (IP/DHCP) or Application Layer (DNS/Firewall) is broken. Use the ipconfig /release and ipconfig /renew commands described above to force a new lease.

Do I need to restart the router to fix Ethernet?

Restarting the router is a valid "Step 4" fix, but it should not be your first move. It’s effective because it reloads the switch firmware and clears the NAT tables, which can fix stuck port states. However, if the issue is a dead cable or a disabled adapter on your PC, restarting the router won’t help. Try the cable check and adapter enabling first. If those fail, then power-cycle the router for 30 seconds.

Can a bad Ethernet cable cause this issue?

Yes, absolutely. A single broken wire among the 8 conductors in a Cat-5e/6 cable can break the 10/100/1000 Mbps negotiation. The port might try to link at 10 Mbps, fail, and time out, showing no light or an intermittent light. Even if the cable looks intact, internal strain on the wires (often from being bent around a sharp corner) can cause this. Always test with a short, certified "known good" cable before blaming the hardware.

Conclusion

Troubleshooting why your Ethernet isn't working while WiFi is fine requires a logical isolation hierarchy. Start at the Physical Layer (cables, ports, LEDs). If that’s clean, move to the Link Layer (adapter status, drivers). Then address the Network Layer (IP, DHCP, TCP/IP stack). Finally, check the Application Layer (DNS, firewall rules).

If you’ve exhausted the software fixes and your port is physically dead, don’t despair. For most users, the most cost-effective immediate solution is a USB-Ethernet adapter for laptops or an external Ethernet switch for routers. Both are inexpensive, plug-and-play solutions that bypass the faulty hardware entirely.

Bookmark this guide for next time you see "connected but no internet" on your wired link. And if you did find the fix, let us know in the comments which step resolved your issue—it helps the next person who lands here with the same headache.

[Download our free 'Network Health Checklist' PDF] [Link Placeholder] to keep your connections stable year-round.

← Back to Home