Your laptop is connected to Ethernet through a USB-C docking station.

The wired network works normally while the computer is awake. You can browse, transfer files, use Remote Desktop, and reach the laptop from other devices.

Then you put the computer to sleep and send a Wake-on-LAN Magic Packet.

Nothing happens.

Or perhaps Wake-on-LAN works from Sleep, but stops working after Hibernate or Shut down.

That difference is the most important clue.

Wake-on-LAN through a USB-C dock requires more than a working Ethernet connection.

For WoL to succeed, four conditions have to remain true:

Supported power state → Active Ethernet path → Wake permission → Correct Magic Packet

If any one of those disappears when the laptop goes to sleep, the Magic Packet never reaches a device capable of waking the computer.

Gate 1: Which Power State Are You Trying to Wake From?

Start here before changing any network settings.

Wake-on-LAN from:

Sleep

is not the same test as Wake-on-LAN from:

Hibernate

or:

Shut down

This matters especially when Ethernet comes from a USB-C dock rather than a built-in RJ45 port.

Some USB-C and USB-based Ethernet solutions can remain available during sleep but lose power in deeper states. Dell's current documentation, for example, shows that some USB-C docks or adapters support WoL only from S3 Sleep, while certain powered docking stations and compatible systems can support S3, S4, and S5. Dell also notes that a basic USB-to-Ethernet adapter may not remain powered in S5, making Wake-on-LAN from complete shutdown impossible on that configuration.

So test the states separately:

If your laptop wakes normally but the dock itself does not restore Ethernet afterward, that is a different issue. See our guide to USB-C hubs not working correctly after sleep.

Gate 2: Does the Dock's Ethernet Connection Stay Alive?

Now put the laptop into the exact power state you are trying to wake from.

Look at the Ethernet port on the dock.

If your dock or router provides link LEDs, ask:

Are the Ethernet lights still active?

If the Ethernet link completely disappears after the computer sleeps or shuts down, the USB Ethernet controller may no longer be receiving enough standby power to listen for a Magic Packet.

That is a hardware/power-state clue, not simply a Windows network-setting problem.

For your first WoL test, use:

Laptop → USB-C Dock → Ethernet → Router/Switch

and keep the laptop charger connected through the dock if your setup supports Power Delivery.

Do not simultaneously troubleshoot:

external SSDs, monitors, webcams, printers, capture cards, and other high-power devices.

Start with Ethernet only.

If ordinary Ethernet itself disconnects, negotiates incorrectly, or disappears through the dock, fix that first with our USB-C Hub Ethernet troubleshooting guide.

Wake-on-LAN cannot work reliably through an Ethernet path that is already unstable while the computer is awake.

Gate 3: Configure the USB Ethernet Adapter, Not the Wrong NIC

A common mistake is changing Wake-on-LAN settings on the laptop's built-in Ethernet or Wi-Fi adapter.

When Ethernet is connected through a USB-C dock, Windows usually sees a separate USB Ethernet adapter.

Open:

Device Manager → Network adapters

Find the Ethernet controller associated with the dock.

Its name may include terms such as:

USB GbE

USB Ethernet

Realtek USB

or another controller name.

Open:

Properties → Advanced

and look for a setting similar to:

Wake on Magic Packet

Set it to:

Enabled

If available, also review:

Wake on Pattern Match

Then open:

Properties → Power Management

and check whether the adapter provides:

Allow this device to wake the computer

For a typical Magic Packet workflow, you can also use:

Only allow a magic packet to wake the computer

if you want to avoid unrelated network traffic waking the PC.

Intel's official WoL guidance also identifies BIOS, driver, operating-system, firewall/router, Wake on Magic Packet, and network-adapter power management as parts of a working WoL configuration. Intel's official Wake-on-LAN setup guidance

Not every adapter exposes the same options.

On some Modern Standby systems, certain Power Management controls may even be unavailable or managed differently by the platform.

Gate 4: Send the Magic Packet to the Right MAC Address

Wake-on-LAN targets a network adapter by its MAC address.

With a docking station, do not automatically use the MAC address printed for:

Wi-Fi

or:

the laptop's built-in Ethernet controller.

The USB-C dock's Ethernet controller may have its own MAC address.

While the laptop and dock are connected, open Command Prompt and run:

ipconfig /all

Find the Ethernet adapter that corresponds to the USB-C docking station.

Record its:

Physical Address

That is normally the first MAC address you should test with your WoL sender.

An exception exists in enterprise environments using MAC Address Pass-Through or another vendor-specific MAC cloning feature. In that case, use the MAC address actually presented by the active Ethernet interface.

Do not guess.

Keep the First Magic Packet on the Local Network

For the first successful test, simplify the network too.

Use another computer or phone connected to the same local network.

Then send the Magic Packet to the dock Ethernet MAC address.

Do not begin by trying to wake the laptop:

from another city

through:

the public internet

across:

VPNs, VLANs, multiple routers, or firewalls.

Intel notes that the wider network configuration also matters for WoL and that routing between systems can affect whether the wake packet reaches the target.

If local WoL works but remote WoL does not, the USB-C dock is probably no longer the main problem.

Investigate:

router configuration → broadcast forwarding → VPN/relay setup → firewall rules

instead.

The Most Useful WoL Test Takes About 10 Minutes

Do not keep changing BIOS and driver settings randomly.

Start with this exact configuration:

1. Connect AC power.

2. Connect the USB-C dock.

3. Connect Ethernet only.

4. Confirm the Ethernet connection works while Windows is awake.

5. Confirm Wake on Magic Packet is enabled on the dock's USB Ethernet adapter.

6. Record the dock Ethernet MAC address.

7. Put the laptop into Sleep.

8. Check whether the Ethernet link LEDs remain active.

9. Send a Magic Packet from another device on the same LAN.

If the laptop wakes

You have proved:

Dock Ethernet + driver + BIOS + Magic Packet + local network

can support at least that sleep state.

Only then test:

Sleep → Hibernate → Shutdown

one at a time.

If Sleep works but Shutdown does not

Stop repeatedly reinstalling network drivers.

First check whether your specific:

Laptop + Dock + USB Ethernet controller

actually supports Wake-on-LAN from S5.

USB-C docking behavior varies significantly between models and power states. Dell's documentation provides a good real-world example: some USB-C adapters support only Sleep-state WoL, while certain powered docks support deeper states with compatible computers.

BIOS and UEFI Still Matter

Even perfect Windows settings cannot override a platform that disables wake events at firmware level.

Restart the laptop and enter BIOS/UEFI.

Depending on the manufacturer, look for settings named:

Wake on LAN

Wake on PME

USB Wake Support

Wake from USB-C Dock

Thunderbolt Wake

Wake from S4/S5

or similar.

The exact names vary by laptop manufacturer.

Intel's WoL documentation also states that system BIOS configuration may be required and recommends checking the computer or motherboard manufacturer's instructions when driver-level settings are already correct.

For business laptops, also check whether WoL is restricted to:

AC power only.

If the laptop wakes when plugged in but never wakes on battery, that may be intentional platform behavior rather than a failed Magic Packet.

What About Windows Fast Startup?

If WoL works from Sleep but not from Windows Shut down, Fast Startup may be worth testing—but only after you confirm the dock and laptop are supposed to support WoL from that power state.

Intel documents Fast Startup as one possible factor in some Ethernet-controller WoL failures from S5.

Do not treat disabling Fast Startup as a universal USB-C dock fix.

If the dock's Ethernet controller loses standby power after shutdown, changing Windows startup behavior cannot make an unpowered Ethernet adapter listen for packets.

That distinction prevents a lot of unnecessary troubleshooting.

When the Dock Is Actually the Limiting Layer

The USB-C docking station becomes the strongest suspect when:

WoL works through the laptop's built-in Ethernet but not the dock;

the dock's Ethernet LEDs shut off in the target sleep state;

the USB Ethernet adapter disappears completely during standby;

or:

the dock manufacturer documents limited WoL power-state support.

At that point, do not evaluate a replacement only by whether it says:

Gigabit Ethernet.

Gigabit Ethernet describes network speed.

It does not automatically mean:

Wake-on-LAN from S3/S4/S5.

For a fixed workstation that also needs charging, Ethernet, display output, and USB peripherals, a USB-C docking station with Gigabit Ethernet and up to 100W Power Delivery can keep the normal wired desk connection and charging path together. The linked LENTION configuration also provides 4K@60Hz HDMI and multiple USB ports. Its current product page displays a $54.59 sale price rather than an Out of Stock notice.

However, use it as a powered Gigabit Ethernet workstation option, not as a guaranteed Wake-on-LAN fix.

LENTION's current product specification does not explicitly advertise WoL support, so WoL should still be verified with the specific laptop, BIOS, operating system, power state, and Ethernet controller before deployment.

For IT Teams, Test WoL Before Standardizing the Dock

If you manage multiple laptops, do not assume that one successful WoL test applies to every model.

Create a small validation matrix:

This is especially useful for:

remote support, patch management, overnight maintenance, classrooms, hot-desking, and enterprise deployments.

WoL is a system-level feature.

The relevant unit of compatibility is not just:

“Does the dock have Ethernet?”

It is:

Does this laptop + firmware + dock + USB Ethernet controller + power state + network support the wake path we require?

Final Takeaway

When Wake-on-LAN does not work through a USB-C docking station, troubleshoot four gates in order:

Power State

→ Ethernet Link

→ Wake Permission

→ Magic Packet Path

Start with:

Sleep + AC power + Ethernet only + same-LAN Magic Packet

If that works, test Hibernate and Shutdown separately.

If Sleep works but Shutdown does not, check the dock and laptop's S5 capability before changing more settings.

If the Ethernet link disappears entirely during sleep, investigate standby power.

If the link stays alive but the computer does not wake, check:

USB Ethernet adapter settings → BIOS/UEFI → MAC address → packet delivery

The key rule is simple:

A working Gigabit Ethernet port does not automatically mean Wake-on-LAN is supported from every power state.

Once you identify exactly where the wake path stops, WoL becomes a compatibility problem you can test instead of a mysterious network failure.