If Windows 11 Ethernet works on one port but not another, the problem usually follows the cable, the port, the negotiation, or the adapter path, not Windows itself. Start with one known-good cable and one known-good port. Then see whether the failure follows the cable or stays with the port. If it stays with one path, fix that part first.
Symptom
You plug the same PC into one Ethernet jack, switch port, router port, dock, or adapter. It works. Then you move to another one, and the link drops, never comes up, or connects with no usable traffic.
Sometimes the bad path looks dead right away. Other times Windows says the adapter is connected, but nothing reaches the network.
That pattern usually means one part of the path is different. The bad part can be the wall jack, switch port, router LAN port, USB-C dock, USB Ethernet adapter, motherboard NIC, cable, or a Windows setting that only affects one adapter path.
Before you start
- Use a known-good Ethernet cable if you have one nearby.
- If you are testing a wall jack or switch port, make sure you know which port is supposed to be used. On a router, plug into the regular Ethernet LAN port, not the Internet port that connects the modem and router.
- If the computer uses a dock or USB Ethernet adapter, note whether the failure happens on the dock path, the built-in motherboard port, or both.
- If the adapter has a driver warning icon or has recently changed behavior, keep that in mind before you change cabling, because driver issues can look like a bad port.
The fastest way to tell what’s broken
- Check the link lights at both ends.
A healthy Ethernet path usually shows a link light on the jack, switch, router, dock, or adapter once the cable is seated. If the light never comes on on the bad path, that port may not be negotiating at all.
If the light comes on but the connection still fails, the physical link exists. The problem is more likely to be speed/duplex, VLAN, driver behavior, or a Windows setting.
- Check Windows 11 adapter status.
Open Settings > Network & internet > Ethernet or open Network Connections and look at the adapter state.
Settings > Network & internet > EthernetIf Windows shows connected but nothing actually passes traffic, the adapter may have a link but still be on the wrong negotiation settings, the wrong VLAN, or the wrong driver path.
- Run a two-swap test.
Use the same known-good cable on the working port first, then on the bad port. After that, use a known-good cable on the bad port. If possible, take the cable that failed and try it on the working port.
- If the problem follows the cable, replace the cable first.
- If the same cable works on one port but not the other, the bad port or adapter path is the likely fault.
- If a dock or USB Ethernet adapter fails only on one USB-C port, suspect the dock, the USB path, power delivery, or firmware instead of the cable.
- If the motherboard Ethernet works but the dock does not, or the dock works but the motherboard port does not, treat those as separate hardware paths, not one shared problem.
If the adapter shows a warning icon in Device Manager > Network adapters, focus on the adapter or driver path before you keep swapping wall jacks. Microsoft’s guidance also says to update the driver, and if that does not work, uninstall the device and restart.
Windows 11 settings and driver issues that can break only one port
Some failures are not physical. They show up only on one Ethernet path because that path uses a different switch, dock, adapter, or negotiated mode.
- Speed and duplex: if one side is forced and the other side is left on auto-negotiation, the link can come up poorly or not pass traffic cleanly. I usually compare the adapter’s speed/duplex setting only after the cable and port swaps already point to the PC path.
- VLAN: a port can be on a different VLAN, or the dock or adapter can be tagged differently from the working path. Windows may still say connected, even though the traffic is not landing where you expect.
- Power-saving behavior: some Ethernet adapters and docks behave differently after sleep, wake, or low-power states. If one path fails only after resume, that points more toward power management or driver behavior than a dead jack.
- Driver and firmware differences: the motherboard NIC, a USB Ethernet adapter, and a dock often use different drivers and sometimes different firmware. One can work while another fails even though the cable and router are fine.
If you need a clean baseline, restart the PC after any driver change. Then test the same cable on the same known-good port again. If the behavior does not change, the fault is probably outside Windows.
What to replace first, and when to stop troubleshooting
Start with the part that failed the two-swap test.
- If the failure follows one cable, replace that cable.
- If the failure stays with one wall jack, switch port, or router port, move to a different port or have that port checked.
- If the failure stays with one dock, USB Ethernet adapter, or motherboard NIC, update the driver first, then replace the device if the problem remains.
- If the failure appears only after a sleep or wake cycle, treat it as a driver or power-management issue before buying hardware.
Microsoft’s Ethernet troubleshooting also starts with the simple physical checks: make sure the cable is in the correct router port and try another Ethernet cable if one is available. In practice, that is the fastest way to avoid reinstalling Windows for a problem that lives in one bad port.
Verify
After the change, connect the same cable to the same path that failed before. Confirm three things: the link light comes on, Windows shows the adapter as connected, and the connection works on the network you expected. If the old path still fails while the new one works, you have isolated the bad part.
If Windows still shows connected but the path does not pass traffic, go back to the isolation test rather than guessing. At that point, the remaining likely causes are the port, the cable, the adapter, the dock, or the negotiated settings on that exact path.
Conclusion
Once you’ve isolated the failure to one cable or one port, replace that part and move on.
Frequently Asked Questions
Can a speed or duplex mismatch make Ethernet work on one port but not another?
Yes. A forced speed or duplex setting on one side and auto-negotiation on the other can give you a link that looks alive but does not pass traffic well. If one port works and another does not, compare adapter settings only after the cable and physical port have been ruled out.
How do I tell if the wall jack or switch port is bad?
Use a known-good cable and a known-good device on the same jack or switch port. If that other device also fails, the port side is the problem. If it works there, the issue is probably the PC, dock, adapter, or driver path.
Sources
- Fix Ethernet connection problems in Windows | Microsoft Support (support.microsoft.com)
- How to fix Ethernet with windows 11 - Microsoft Q&A (learn.microsoft.com)