USB-C hub Ethernet not working: the 7 causes, in order

Damian Krzyzanowski

"USB-C hub Ethernet not working" is one of the most-searched problems in this whole category, and it shows up around every major hub brand, Anker, Satechi, Belkin, Vava, and plenty of others, because the underlying causes have almost nothing to do with which brand you bought. Work through these seven in order. Most people find the answer in the first three.

1. Check the hub is getting enough power

The single most common cause. Many hubs, especially ones bundling Ethernet with a display output and extra USB ports, draw more power than a laptop's USB-C port alone reliably supplies, particularly once you've also got a monitor and a couple of peripherals hanging off the same hub. Ethernet is often the first port that drops out under a power shortfall, since the hub prioritizes what it can still power. Plug the hub into its own power adapter if it has a power-input port, or unplug non-essential peripherals and see if Ethernet comes back.

2. Confirm the driver actually loaded

Most USB-C hub Ethernet ports use Realtek's RTL8153 chipset, and it's in-box on current Windows and macOS, meaning no separate installer should be needed. Older Windows builds, and some minimal Linux installs, are the exception. On Windows, check Device Manager for the adapter under Network Adapters and look for a warning icon. On macOS, check System Settings > Network for the adapter listing. If it's missing entirely rather than just disconnected, that points at a driver problem rather than a physical one.

3. Make sure the port itself carries data

Not every USB-C port on a laptop is equal. Some are wired for charging only, and plugging a hub into one of those will power the hub's lights without ever passing Ethernet or USB data through it. If your laptop has more than one USB-C port, try the others before assuming the hub itself is faulty.

4. Check the adapter isn't just disabled or deprioritized

Both Windows and macOS will happily show a working Ethernet adapter that still isn't being used, because Wi-Fi is set as the preferred connection. This looks identical to "not working" from the user's side: no traffic appears to be moving over the cable. Check the adapter isn't disabled in Network Adapters (Windows) or the network service list (macOS), and check your network preference order if both Wi-Fi and the hub's Ethernet are active at once.

5. Rule out the cable, both of them

Two cables can be the problem here: the USB-C cable between the hub and your machine, and the Ethernet cable between the hub and your router or switch. A USB-C cable built for charging only, with no data lines wired, will power the hub but never carry Ethernet traffic through it. An Ethernet cable with a damaged connector will show no link light on the hub. Swap each independently to isolate which one is actually at fault.

6. Consider whether the hub is oversubscribed

Hubs that share a single upstream USB connection across Ethernet, an external display, and storage all at once can run into real bandwidth or power contention when everything is plugged in and active simultaneously. Ethernet is often the first thing to drop when this happens, since it's rarely the port a hub's firmware prioritizes over video output. Unplug the display and storage temporarily and see if Ethernet becomes stable.

7. Check for a known compatibility quirk with your specific machine

The rarest cause, and the one worth checking last: some hub and laptop combinations have documented firmware compatibility issues, particularly around Thunderbolt versus plain USB-C ports on the same machine behaving differently. Check the hub manufacturer's support site for your specific laptop model and consider a firmware update if one's available before concluding the hub itself is defective.

Every USB-C hub and dock we stock names its Ethernet chipset (RTL8153, AQC113 on higher-bandwidth models) right in the listing, so you know what you're troubleshooting from day one. See what we stock, or ask us about a specific compatibility question.