Ethernet not working? 6 home checks before calling a technician
Most home Ethernet faults come down to one of three things: a damaged cable or loose port, a driver or network stack glitch, or a router and ISP problem. Start by swapping the cable, checking the LED lights on both ends, and restarting the router and PC. If the connection still won’t come up, isolate the fault with a second device, and if the port or cabling is dead, book an on-site technician.
TL;DR:
A known good Cat5e or Cat6 cable can reveal internal wire damage that is invisible outside; temporarily disable VPNs, proxies, or third party firewalls.
Windows network commands clear separate layers, so run Winsock reset, TCP/IP reset, release, renew, and DNS flush in that order; reserve Network reset for last.
On a Mac, confirm Ethernet shows as connected and renew the DHCP lease; USB or Thunderbolt adapters appear as separate named services.
Arrange technician help for dead wall ports, damaged cabling, or a network card that fails swap testing; note error messages and light status first.
Table of Contents
Windows troubleshooting: adapter, drivers and network commands
Mac and Linux checks: DHCP, adapter identification and simple commands
Router, modem and wall port checks: testing cabling at the source
Drivers, adapters and hardware faults: tests and replacement guidance
Isolate the problem: a minimal-device test and what the result means
When to call an on-site technician and what to expect from a visit
Quick troubleshooting checklist: six fast checks in order
Before diving into settings menus, run through this five to fifteen minute routine. It catches the majority of Ethernet faults without needing any technical background.
Swap the Ethernet cable for a known-good Cat5e or Cat6 cable, since internal wire damage is common and invisible from the outside.
Reseat both ends of the cable firmly and check the LED lights on the router and the PC’s network port.
Restart the modem or router first, wait a minute, then restart the PC and test again.
Temporarily disable any VPN, proxy or third-party firewall software that could be blocking the connection.
Plug a second device, or a USB-to-Ethernet adapter, into the same cable and port to see if the fault follows the hardware.
If nothing changes, note down what you’ve tried and move on to platform-specific steps or call a technician.
Pro Tip: Always test with a different cable before touching any settings, a damaged cable is the single most common cause of a dead Ethernet connection.
Windows troubleshooting: adapter, drivers and network commands
Windows 10 and 11 give you a few built-in tools that resolve most wired connection issues without reinstalling anything major.
Open Settings, go to System, then Troubleshoot, and run the Network and Internet troubleshooter under Get Help.
In Settings → Network & Internet, or in Device Manager, disable the Ethernet adapter, wait ten seconds, then re-enable it.
If the adapter still shows errors, update the driver first. If that fails, roll it back, and if that fails, uninstall it and let Windows reinstall it on restart.
Before uninstalling any driver, download the correct one from the manufacturer’s site on another device and transfer it by USB, since you’ll have no internet access to fetch it afterwards.
Open Command Prompt as administrator and run netsh winsock reset, then netsh int ip reset, then ipconfig /release, ipconfig /renew and ipconfig /flushdns in that order.
As a last resort, use Windows’ “Network reset” option, which removes and reinstalls every network adapter on the machine.
Most Windows Ethernet problems are resolved through this exact sequence: cable checks, the built-in troubleshooter, a TCP/IP reset and, if needed, a driver reinstall. Running the commands in order matters, since each one clears a different layer of the network stack.
Mac and Linux checks: DHCP, adapter identification and simple commands
macOS and Linux handle Ethernet differently, but the checks are just as quick.
On a Mac, open System Settings → Network and confirm the Ethernet service shows as connected, not just listed.
If you’re using a USB or Thunderbolt adapter, it will appear as its own named service rather than “Ethernet”, so check that the right one is selected.
In Network settings, click Details on the Ethernet service and renew the DHCP lease, then restart both the Mac and the Ethernet device.
Apple’s own troubleshooting guidance covers cable checks, adapter naming and DHCP renewal as the standard first steps.
On Linux, run ip addr to confirm the interface is listed, then sudo dhclient to request a new lease.
Bring the interface down and back up with sudo ip link set eth0 down followed by up, and check dmesg for driver errors if it won’t come up.
If your Mac or Linux machine has no built-in Ethernet port, test with a different adapter or device before assuming the computer itself is at fault.
Router, modem and wall port checks: testing cabling at the source
If the cable and adapter check out, the fault may sit further back, in the router, the wall jack, or the line coming into the house.
Check the LED lights on every LAN port on the router, not just the one you’re using, and try a different port.
Bypass any unmanaged switch between the router and your PC and connect the cable directly to the modem or router.
If your property uses FTTN, FTTB or older in-wall copper wiring, watch for symptoms like a connection that drops under load or only works at a lower-than-expected speed, both signs of degraded cabling.
ACMA’s guidance on home cabling recommends using Cat5 or better for in-home data wiring and contacting a registered cabler for any wiring changes.
If every device in the house loses connection at once, or your provider has published an outage notice, the fault is more likely upstream than in your own setup.
Pro Tip: If devices on other rooms’ wall ports also fail, suspect the in-wall cabling or the NBN connection box rather than your PC.
Telcos also carry obligations here: under ACMA’s NBN connection rules, your provider must test that your service is actually working after any migration and keep you connected during the move, so a sudden total outage straight after a provider change is worth raising with them directly.
Drivers, adapters and hardware faults: tests and replacement guidance
Once you’ve ruled out cabling and the router, the remaining fault sits in either the network stack or the hardware itself, and the symptoms usually tell you which.
A driver or stack problem typically shows as “Unidentified network”, repeated IP configuration errors, or a connection that works briefly then drops.
A hardware fault usually shows as “network cable unplugged” in Windows despite a connected cable, or LED lights that never light up at all.
To confirm a failed network card, plug in a cheap USB-to-Ethernet adapter. If that gets a link light and connects, the onboard port or NIC has failed.
Testing the same cable and port on a second PC is the other quick way to confirm whether the fault travels with the device or stays with the port.
For replacements, a standard Cat6 cable and a basic USB-to-Ethernet adapter are reliable first swaps, branded “gaming” cables rarely outperform standard Cat6 in typical home setups.
Isolate the problem: a minimal-device test and what the result means
A simple swap test tells you almost everything you need to know before calling anyone.
Connect a second device to the same cable and port: if it works, the original PC or its adapter is the likely fault.
If both devices fail on the same port, suspect the cable, the port itself, or the connection coming in from your provider.
If the connection drops intermittently rather than failing outright, log the time, what you were doing, and whether a restart fixed it.
Before contacting support, write down any error messages, the state of the LED lights, and which commands you’ve already run.
When to call an on-site technician and what to expect from a visit
Some faults are faster and safer to fix with a technician on site than through more remote troubleshooting.
A wall port that never shows link lights, visibly damaged in-wall cabling, or a NIC that still fails after a swap test are the clearest signs it’s time to call someone.
A technician will typically run continuity checks on the cable, use a cable tester, swap ports and devices to confirm the fault, check router diagnostics, and reinstall drivers if needed.
Have your error messages, the troubleshooting steps you’ve already tried, and your router’s make and model ready before the call.
Technician visits can be arranged locally, and you only pay once the connection’s actually working again. Book through our Brisbane in-home tech support page or our laptop and computer repair service if the fault points to the PC itself.
A practical troubleshooting perspective
The biggest time waster we see is people reinstalling drivers three or four times before ever testing with a second device or cable. A single swap test tells you more in two minutes than an hour of driver tinkering. If your Ethernet drops only sometimes, write down when it happens, that pattern is the most useful thing you can hand a technician.
— Matthew
Get your wired connection sorted at home
Ethernet faults are handled plainly, with no hidden fees, and payment is required only once the fault is resolved. A No Fix, No Fee guarantee covers same-day home visits in serviced areas.
Book a visit through our Wi-Fi and internet support page, or our laptop and computer repairs page if the fault looks device-related.
Have your router’s make and model, any error messages, and the troubleshooting steps you’ve tried ready for the technician.
Readers in Logan or Ipswich can book directly through our Logan or Ipswich service pages.
FAQ
My Ethernet cable isn’t working. What can I do to fix this?
Swap it for a known-good Cat5e or Cat6 cable first, since internal wire damage is common and often invisible. If the new cable still shows no link lights on either end, test the same port with a different device to confirm whether the fault is the cable, the port or the PC.
What is the 5-4-3 rule of Ethernet?
It’s an older Ethernet networking guideline limiting a network segment to five cable sections, four repeaters or hubs, and three populated segments, from the days of shared coaxial and hub-based networks. It rarely applies to modern home setups, which use switched Ethernet rather than shared hub segments.
Is Wi-Fi faster than Ethernet?
Not typically. A wired Ethernet connection usually delivers more consistent speed and lower latency than Wi-Fi because it isn’t affected by wireless interference, distance or competing devices on the same channel.
How do I fix an unidentified network error?
Start with Windows’ built-in Network and Internet troubleshooter, then run ipconfig /release followed by ipconfig /renew to force a fresh IP address. If the error persists, reset the TCP/IP stack with netsh int ip reset and restart the PC.
Sources
Recommended
Comments