Why Doesn't My Computer Detect My Ethernet Connection?
Diagnose Ethernet that shows no usable wired connection by starting with physical link, then isolating cable, router or switch port, built-in adapter, USB or dock hardware, driver state, and only afterward DHCP or internet configuration.
If an Ethernet connection is not detected, start at the physical link.
There is no point changing DNS or IP settings before proving that the computer and the router, switch, dock, or adapter can establish link at all.
Switchboard Tech Services offers local Kirksville wired-network diagnosis for built-in Ethernet, USB Ethernet adapters, and dock-based network connections.
Check for physical link first
Many Ethernet ports have indicator lights.
When a working cable connects a working adapter to an active router or switch port, one or both ends often show link activity.
If neither end indicates link, focus first on:
- cable;
- router or switch port;
- computer Ethernet port;
- USB Ethernet adapter;
- dock;
- hardware enablement.
Link lights are useful evidence, though not every device exposes them clearly.
Test a known-good cable and port
A cable can fail internally while looking perfect from the outside.
Use a known-good cable if possible.
Then test another known-good router or switch port.
This produces a simple matrix:
- same computer, different cable;
- same cable, different port;
- another known-good device on the same cable and port.
Cross-testing is faster than guessing.
Built-in Ethernet and USB/dock Ethernet are different branches
A desktop with a motherboard Ethernet jack has fewer layers than a laptop using:
USB-C port → dock → Ethernet chipset → cable → router.
If Ethernet arrives through a dock or USB adapter, test whether:
- the dock itself is detected;
- other dock functions work;
- the USB-C port supports the required data mode;
- the Ethernet adapter appears in Windows;
- another direct USB Ethernet adapter works where practical.
A cable fitting into the dock does not prove the dock's Ethernet chipset is functioning.
Check Windows adapter detection
Device Manager and Windows network settings can show whether the Ethernet adapter exists from the operating system's perspective.
If the adapter is missing or has an error state, investigate the driver or hardware.
Use official Windows, OEM, dock-maker, or chipset drivers where appropriate.
Microsoft's current Ethernet troubleshooting guidance still uses Device Manager for adapter-driver repair and recommends having the correct manufacturer driver available before uninstalling a broken adapter driver.
Built-in LAN can be disabled
Some computers allow onboard Ethernet to be disabled in firmware or manufacturer settings.
That is more plausible after firmware changes, repairs, or configuration work.
Do not change unrelated firmware settings.
Identify the exact model and current configuration first.
Consider physical damage
Ethernet jacks can be damaged.
Clues include:
- broken retaining tabs;
- bent contacts;
- intermittent link when the plug moves;
- visible debris;
- no link with multiple known-good cables and switch ports.
Board-level port repair is outside ordinary software troubleshooting.
On suitable computers, a USB Ethernet adapter may be a practical alternative if the built-in port has failed.
Only troubleshoot DHCP and internet after link exists
Once Windows shows a stable Ethernet link, then ask whether the computer receives:
- a normal local IP;
- gateway;
- DNS configuration;
- internet access.
If link exists but the PC reports Connected, No Internet, that belongs to the next network layer.
If link does not exist, changing DNS will not create it.
The correct order is physical link first, adapter detection second, address configuration third, internet access last.
For a related next step, see Why Does My Computer Keep Disconnecting From Wi-Fi? and Why Is Wi-Fi Slow on One Computer but Fine on Everything Else?.
For authoritative guidance on this subject, see Microsoft's Windows backup guidance.
See Also
- Categories: Home Networking & Wi-Fi
- Tags: #Drivers, #Network Troubleshooting, #Ethernet