What Is Wake-on-LAN (WoL)? How It Works, Magic Packets, Benefits, Security Risks, History, Setup and Troubleshooting

Quick Answer

Wake-on-LAN (WoL) is a network and hardware power-management technology that allows a compatible computer to be awakened remotely by sending a specially constructed network message—usually called a Magic Packet—to its network interface.

The computer may appear to be sleeping, hibernating, or in some hardware configurations even shut down, but part of the network interface remains powered and monitors the network for an authorized wake pattern. When the NIC detects the correct Magic Packet containing its MAC address, it signals the motherboard to wake the computer.

WoL is particularly useful for:

• remotely managed office computers
• IT maintenance after business hours
• software deployment and patching
• backup operations
• remote-support environments
• RDP/remote-access systems
• labs and classrooms
• reducing unnecessary PC power consumption

However, WoL should not be confused with secure remote authentication. A conventional Magic Packet is normally not authenticated or encrypted, so network design and access controls are important when WoL is used outside a trusted LAN.

What Does Wake-on-LAN Mean?

Wake-on-LAN is commonly abbreviated as:

WoL or WOL

The basic idea is simple:

A computer can enter a low-power state while its network interface continues listening for a special network message that tells the system to wake.

Microsoft describes WoL as functionality in which a network adapter detects a wake event—typically a specially constructed Ethernet packet—and causes the computer to return from a low-power state.

It therefore solves an important problem.

Suppose an organization has 200 desktop computers. Leaving all 200 computers running 24 hours a day simply so administrators can access them after hours wastes energy.

Turning them off or putting them to sleep saves power, but then how does the administrator remotely access them at night?

Wake-on-LAN provides one answer:

Sleep PC → Send Magic Packet → PC wakes → Perform maintenance → Return PC to sleep

A Simple Wake-on-LAN Example

Imagine an office PC called:

ACCOUNTS-PC01

Its Ethernet adapter has the following MAC address:

00-1A-2B-3C-4D-5E

At 11:00 PM, an administrator wants to remotely install updates.

Instead of leaving ACCOUNTS-PC01 running all day and night:

1. The computer is allowed to sleep after office hours.
2. The network adapter remains capable of detecting WoL traffic.
3. The administrator's management system sends a Magic Packet containing 00-1A-2B-3C-4D-5E.
4. The Ethernet controller detects its MAC address inside the Magic Packet.
5. The NIC generates a wake event.
6. The motherboard restores the computer to an operating state.
7. Windows starts/resumes.
8. The administrator connects to it and performs the maintenance.

That is Wake-on-LAN in practical terms.

History of Wake-on-LAN

Wake-on-LAN is not a new Windows feature. Its roots go back to the power-management and network-management work of the 1990s.

AMD and Magic Packet Technology

One of the most important milestones came from AMD and Hewlett-Packard, which worked on what became Magic Packet Technology.

AMD published its Magic Packet Technology white paper in November 1995. The paper described a mechanism that allowed a networked "Green PC" to enter a low-power state while its Ethernet controller continued watching for a special data pattern that could wake the machine.

This addressed a growing problem of the era.

Businesses wanted PCs to save electricity when they were not being used, while IT departments still needed the ability to remotely:

• perform backups
• install software
• perform maintenance
• run diagnostics
• update systems

AMD's subsequent historical material shows Magic Packet technology being co-developed with Hewlett-Packard, incorporated into IBM Wake-on-LAN systems, licensed to Ethernet-controller manufacturers, and integrated with broader PC power-management initiatives during the second half of the 1990s.

IBM and Intel

Wake-on-LAN gained further industry momentum when IBM and Intel collaborated on enterprise PC manageability.

In October 1996, Intel announced an alliance with IBM aimed at reducing PC ownership and administration costs. One of the areas specifically identified was IBM's Wake-on-LAN capability combined with Intel networking technology.

By 1997 Intel was incorporating Magic Packet filtering and Wake-on-LAN functionality into Ethernet products.

Over time, remote wake capabilities became common in business-class desktop PCs, motherboards and Ethernet controllers.

Why Was Wake-on-LAN Invented?

WoL emerged largely because of two conflicting requirements:

Requirement 1 — Save electricity

Organizations wanted unused computers to enter low-power states.

Requirement 2 — Keep computers manageable

IT administrators needed to reach computers for:

• backup
• software installation
• antivirus scanning
• inventory
• troubleshooting
• operating-system maintenance

A PC that was completely inaccessible while sleeping made centralized administration difficult.

Wake-on-LAN helped bridge that gap.

How Does Wake-on-LAN Work?

The process involves several components:

Sending device → Network → NIC → Motherboard/Firmware → Computer

The network adapter plays the most important role.

When the computer enters a supported low-power state, enough circuitry remains powered for the NIC to monitor incoming network traffic.

The NIC looks for a recognized wake pattern.

For traditional WoL, that pattern is usually the Magic Packet.

When the correct pattern is detected:

1. NIC recognizes the Magic Packet.
2. NIC generates a hardware wake event.
3. The motherboard receives the event.
4. Power-management circuitry changes the system's power state.
5. The CPU, memory and other hardware become operational.
6. The operating system resumes or boots.

ACPI specifications explicitly account for network devices recognizing wake frames, including Magic Packets and other management requests.

What Is a Magic Packet?

The Magic Packet is the best-known component of Wake-on-LAN.

Despite the name, there is nothing mysterious about it. It is simply a network frame containing a distinctive byte pattern that the sleeping network controller recognizes.

The classic Magic Packet sequence starts with:

FF FF FF FF FF FF

followed by the target network adapter's 48-bit MAC address repeated 16 times.

AMD's original Magic Packet specification describes the Ethernet controller scanning incoming frames for this sequence.

For example, suppose the target MAC address is:

00:11:22:33:44:55

Conceptually, the relevant payload contains:

FF FF FF FF FF FF
00 11 22 33 44 55
00 11 22 33 44 55
00 11 22 33 44 55
...
(repeated 16 times)

The NIC does not need Windows to be actively processing normal network applications to recognize this pattern. Detection occurs at the network-controller/hardware level.

Why Does Wake-on-LAN Use the MAC Address?

A sleeping computer may not have its normal operating-system network stack running.

Therefore, relying only on an IP address would be problematic.

The MAC address identifies the target network interface.

For example:

3C-52-82-AB-CD-EF

A WoL application generally asks for the MAC address of the computer you want to wake.

You can find a Windows PC's MAC address using:

ipconfig /all

Look for:

Physical Address

Another useful command is:

getmac

These commands do not require administrator rights merely to display normal adapter information.

Does Wake-on-LAN Use an IP Address?

The answer is:

Not for identifying the sleeping NIC inside the classic Magic Packet.

The identifying information is its MAC address.

However, IP networking may still be involved in transporting the packet.

Many WoL utilities encapsulate the Magic Packet inside UDP and send it to a broadcast address.

Ports commonly used by WoL utilities include:

• UDP 7
• UDP 9

These port numbers are conventions used by implementations; the core Magic Packet mechanism is based on the recognizable payload rather than requiring a specific TCP/UDP application port.

Broadcast Traffic and Wake-on-LAN

WoL packets are frequently sent as broadcasts because a sleeping machine may not participate normally in IP networking.

For example, a network could be:

192.168.1.0/24

with a broadcast address:

192.168.1.255

A WoL application could send the Magic Packet toward the broadcast network.

Every NIC receiving the broadcast can examine it, but only the NIC whose configured MAC address matches the Magic Packet should trigger the wake event.

Can Wake-on-LAN Work Across Different Subnets?

This is where WoL becomes more complicated.

Routers normally separate broadcast domains, and traditional WoL commonly depends on broadcast delivery. Intel's current guidance notes that ordinary WoL configurations are generally simplest when sender and target are on the same subnet.

Cross-subnet WoL can nevertheless be implemented using technologies such as:

• directed broadcasts
• WoL relay agents
• management servers
• router-specific WoL functions
• VPN-connected management networks
• an always-on device inside the destination LAN

For business networks, using an authenticated management system or trusted WoL relay is generally preferable to exposing WoL directly to the public Internet.

Can Wake-on-LAN Work Over the Internet?

Technically, remote wake across routed networks is possible, but simply forwarding a UDP port from the Internet is not the best security architecture.

A safer model is usually:

Internet → VPN → Trusted LAN/WoL relay → Magic Packet → Target PC

Another option is:

Management server → Remote site agent → Target PC

This provides much better control than indiscriminately accepting public WoL traffic.

Wake-on-LAN vs Wake-on-WAN

You may encounter the term Wake-on-WAN.

Wake-on-LAN generally means waking a device from its local network.

Wake-on-WAN usually describes arrangements in which the wake request originates outside that LAN.

Wake-on-WAN therefore isn't necessarily a fundamentally different Magic Packet technology. It is primarily about how the wake request reaches the destination network.

What Hardware Is Required for Wake-on-LAN?

Several components must cooperate.

This explains why enabling one Windows checkbox does not guarantee that WoL will work.

Common BIOS/UEFI Wake-on-LAN Settings

The terminology differs between manufacturers.

Look for options such as:

• Wake on LAN
• Wake on PCI-E
• Wake on PCIe
• Wake on PME
• Power On By PCI-E
• Resume By LAN
• LAN Power On
• PCI Device Power On

Intel notes that firmware WoL options are commonly found in a BIOS/UEFI power-control section and may be called Wake on LAN or Wake on PME.

Do not randomly enable unrelated wake settings. Check the motherboard or system manufacturer's documentation when available.

What Is PME?

PME means Power Management Event.

PCI/PCI Express devices can signal that an event has occurred which requires the system to wake.

In a WoL scenario:

Magic Packet → NIC → PME/wake signal → Motherboard → System wakes

Older add-in NIC implementations could also use dedicated WoL cables, whereas modern integrated and PCI Express hardware normally handles wake signalling through the platform/bus power-management architecture.

Wake-on-LAN and Windows Power States

Understanding power states is important because "the computer is off" can mean several technically different things.

Microsoft currently documents WoL support from S3 and S4 in the Windows power model, while noting that S5 wake is not officially supported by Windows itself, although some firmware can arm the NIC independently.

That distinction is important.

A motherboard may successfully wake from shutdown even when Windows documentation doesn't define that as an OS-controlled S5 WoL scenario.

Why Wake-on-LAN Cannot Work Without Electricity

WoL is sometimes mistakenly described as remotely turning on a completely unpowered PC.

It cannot do that.

Some circuitry must remain powered so that the network adapter can detect the wake packet.

Therefore WoL cannot work if:

• AC power is disconnected
• PSU switch is off
• power strip is off
• laptop battery is completely discharged and no external power is available
• motherboard removes all standby power from the NIC
• the system is in mechanical-off state G3

Think of the NIC as a sleeping security guard.

The building may appear closed, but someone must remain awake to hear the doorbell.

How to Enable Wake-on-LAN in Windows

The exact options depend on your NIC and driver.

Step 1 — Enable WoL in BIOS/UEFI

Restart the computer and enter BIOS/UEFI.

Look under areas such as:

Power Management

or:

Advanced → Power

Enable the relevant Wake-on-LAN/PCIe/PME option.

Save changes and boot Windows.

Step 2 — Open Device Manager

Press:

Win + X

Select:

Device Manager

Expand:

Network adapters

Right-click your Ethernet adapter and select:

Properties

Step 3 — Check the Advanced Tab

Look for settings such as:

Wake on Magic Packet

Set it to:

Enabled

Depending on the adapter, you may also see:

• Wake on Pattern Match
• Shutdown Wake-On-Lan
• Wake from S5
• PME
• Wake on Link

The exact options vary by manufacturer and driver.

Intel's current setup guidance specifically includes enabling Wake on Magic Packet and configuring the NIC's wake-related power-management settings where supported.

Step 4 — Configure Power Management

Open:

Network Adapter → Properties → Power Management

Common options include:

Allow this device to wake the computer

and:

Only allow a magic packet to wake the computer

For a conventional WoL setup, these are often useful.

Restricting wake events to Magic Packets can also help prevent unwanted wakeups caused by ordinary network patterns.

Useful Windows Commands for Wake-on-LAN Troubleshooting

Windows includes useful powercfg diagnostics.

Find Devices Currently Allowed to Wake Windows

Open Command Prompt and run:

powercfg /devicequery wake_armed

Microsoft documents wake_armed as listing devices currently configured to wake the system.

Your Ethernet adapter should normally appear here when it is armed as a Windows wake source.

Find Wake-Capable Devices

Run:

powercfg /devicequery wake_programmable

This displays devices that Windows considers configurable as wake sources.

Find What Last Woke the Computer

Run:

powercfg /lastwake

This is particularly useful when a computer wakes unexpectedly.

Microsoft documents /lastwake as reporting information about the most recent system wake transition.

Wake on Magic Packet vs Wake on Pattern Match

These settings should not be confused.

Wake on Magic Packet

The NIC specifically looks for the WoL Magic Packet containing its MAC address.

Wake on Pattern Match

The NIC may wake when certain other network patterns are detected.

Intel documentation gives examples including certain incoming TCP connections and network authentication traffic on supported adapters.

For a PC that wakes unexpectedly, consider disabling:

Wake on Pattern Match

while leaving:

Wake on Magic Packet

enabled, if that configuration is supported by the adapter.

What Is Wake on Wireless LAN?

Traditional WoL is most strongly associated with wired Ethernet.

Wireless systems may instead support:

Wake on Wireless LAN (WoWLAN)

Wi-Fi wake behavior is more complex because maintaining wireless association, authentication and low-power connectivity involves more than simply keeping an Ethernet PHY listening.

Support depends heavily on:

• wireless adapter
• driver
• firmware
• operating system
• access point
• sleep state
• manufacturer implementation

Do not assume that a laptop supporting Ethernet WoL automatically supports equivalent Wi-Fi wake behavior.

Modern Standby and Wake-on-LAN

Modern Windows computers may use Modern Standby instead of traditional S3 sleep.

This changes the power-management model.

Microsoft specifically warns against enabling legacy S3 WoL on a Modern Standby-capable system because Magic Packet wake is already integrated into Modern Standby and inappropriate legacy configuration can cause network problems.

Therefore, advice written for older Windows desktops should not automatically be applied to every modern laptop.

Wake-on-LAN and Windows Fast Startup

Fast Startup can cause confusion when testing WoL.

Windows Fast Startup is not identical to a traditional full S5 shutdown. It uses a hibernation-related mechanism for the kernel session.

Microsoft's WoL documentation explains that Windows shutdown/power-state behavior can affect whether a NIC remains armed for wake.

Therefore, a PC may:

• wake successfully from Sleep
• wake from Hibernate
• fail after Shut down

That does not necessarily mean the NIC is defective.

The power state and firmware implementation may simply differ.

Benefits of Wake-on-LAN

1. Reduced Energy Consumption

Computers do not need to remain fully operational simply because someone might need remote access later.

Organizations can allow systems to sleep and wake them when required.

Microsoft Research has explored this exact concept: allowing enterprise computers to sleep more aggressively while providing network-triggered wake capability when remote access is required.

2. Remote IT Maintenance

Administrators can wake systems before:

• patch deployment
• antivirus scans
• software installation
• backups
• inventory scans
• diagnostics

This is one of the original motivations behind the technology.

3. Better Remote-Desktop Availability

Suppose you need RDP access to your office computer from home.

Instead of keeping the PC running continuously:

Connect securely to company network → Send WoL request → PC wakes → Connect using RDP

This can reduce unnecessary runtime.

4. Scheduled Maintenance

An organization might wake 100 PCs at 2:00 AM, perform maintenance, and return them to sleep afterward.

AMD was describing scheduled remote wake scenarios for backups, software installation, diagnostics and virus checks as far back as the 1990s.

5. Centralized Administration

WoL works particularly well with endpoint-management systems.

Administrators can manage computers without physically walking to each desk to press a power button.

6. Useful for Home Labs

WoL can also be useful for:

• home servers
• NAS-related environments
• test PCs
• development systems
• media computers
• lab machines

A machine can remain asleep until needed.

Does Wake-on-LAN Save Electricity?

Potentially, yes.

WoL itself does not magically reduce power consumption. The savings come from allowing the computer to spend more time in a low-power state instead of remaining fully powered solely for remote accessibility.

There is still a small standby-power requirement because the motherboard and/or network interface needs enough power to detect a wake event.

So:

WoL enabled + PC sleeping

generally consumes much less energy than:

PC fully running 24×7

but not literally zero power.

Is Wake-on-LAN Secure?

This requires an important distinction.

Wake-on-LAN is a wake mechanism, not a login mechanism.

The traditional Magic Packet is primarily designed to identify the NIC to wake, not to provide modern cryptographic authentication.

Therefore, possession of a computer's MAC address may be enough for someone who can reach the relevant broadcast/network path to construct a conventional wake packet.

However, waking a computer is not the same as logging into it.

An attacker still needs to defeat whatever security protects the operating system and services.

For example:

WoL packet → PC wakes

does not mean:

WoL packet → attacker automatically logs into Windows

These are separate security events.

Security Risks of Wake-on-LAN

1. Unauthorized Wakeups

Someone with network access may be able to wake machines without authorization.

Possible consequences include:

• unnecessary electricity use
• devices waking outside office hours
• unexpected system activity
• increased exposure time of network services

2. Increased Attack Surface After Wake

A sleeping PC may expose little or no normal network service.

Once awakened, services such as:

• RDP
• SMB
• web servers
• remote-management agents

may become reachable.

The main security concern therefore isn't necessarily the Magic Packet itself; it is what becomes accessible after the computer wakes.

3. Public Internet Exposure

Directly forwarding WoL-related broadcast traffic from the public Internet is generally poor practice.

It introduces unnecessary exposure and can require risky router configurations.

A VPN, management gateway or authenticated relay is preferable.

4. Directed Broadcast Abuse

Subnet-directed broadcasts need careful handling.

Broad forwarding of directed broadcasts has historically been associated with amplification attacks. Network administrators should therefore avoid enabling unrestricted directed broadcasting simply to make WoL convenient.

5. MAC Addresses Are Not Passwords

A MAC address should never be treated as a secret authentication credential.

It is an identifier.

Do not design security around the assumption that knowing a MAC address proves the sender is authorized.

Wake-on-LAN Security Best Practices

For business environments:

1. Prefer WoL inside trusted management networks.
2. Use VPN access for remote administrators.
3. Avoid exposing WoL directly to the Internet.
4. Restrict directed broadcasts.
5. Segment management traffic where appropriate.
6. Use firewall rules.
7. Protect RDP and other remote services independently.
8. Require strong authentication after the PC wakes.
9. Use MFA where supported by the remote-access solution.
10. Disable WoL on machines that do not require it.
11. Prefer Magic Packet-only wake where appropriate.
12. Keep NIC drivers and firmware updated.

The important principle is:

WoL should wake the computer; your security controls should decide who can actually use the computer.

Does Wake-on-LAN Bypass a Windows Password?

No.

Wake-on-LAN does not normally bypass:

• Windows password
• PIN
• BitLocker authentication
• domain authentication
• RDP authentication
• application passwords

It only causes a supported machine to wake or power up.

Normal authentication still applies afterward.

Does Wake-on-LAN Work If the PC Is Completely Powered Off?

Sometimes people answer this with a simple "yes," but that can be misleading.

The correct answer is:

It depends on what "off" means and on the hardware/firmware implementation.

A system in S5 may appear completely off while still receiving standby power.

Some motherboards can keep the NIC sufficiently powered and respond to WoL from S5.

Microsoft notes, however, that Windows itself does not officially support WoL from S5, although firmware on some systems can provide such capability.

If the AC power is physically removed, conventional WoL cannot work.

Why Does the Ethernet LED Stay On When the PC Is Off?

This often surprises users.

If WoL is enabled, you may notice that the Ethernet port LEDs remain illuminated or blink even after Windows has shut down.

This can indicate that part of the NIC is still receiving standby power.

That is exactly what may be required for the adapter to detect the Magic Packet.

It is not necessarily a fault.

Wake-on-LAN Troubleshooting

Problem 1 — WoL Works from Sleep but Not Shutdown

Possible causes:

• S5 wake unsupported
• firmware does not arm NIC during shutdown
• Fast Startup behavior
• driver configuration
• motherboard power-saving option
• NIC loses standby power

First test WoL from Sleep.

If that works, the network and Magic Packet mechanism are probably functioning, and the remaining issue is likely related to the shutdown power state.

Problem 2 — Ethernet Light Goes Off Completely

If the NIC loses all power after shutdown, it cannot listen for Magic Packets.

Check:

• BIOS/UEFI WoL settings
• ErP/EuP power-saving settings
• PCIe power settings
• NIC driver settings
• motherboard documentation

Some aggressive standby-power-saving modes intentionally remove power from network hardware.

Problem 3 — Computer Wakes Randomly

Run:

powercfg /lastwake

Then:

powercfg /devicequery wake_armed

If the NIC is responsible, consider disabling:

Wake on Pattern Match

and retaining only:

Wake on Magic Packet

where appropriate.

Problem 4 — WoL Works on Same LAN but Not Remotely

This is common.

Possible reasons:

• routers don't forward broadcast traffic
• VLAN separation
• directed broadcasts disabled
• firewall rules
• ARP behavior
• NAT configuration
• VPN restrictions

Use a secure WoL relay or endpoint-management system rather than immediately opening ports on the router.

Problem 5 — WoL Stopped Working After Driver Update

Check Device Manager again.

Driver updates can change or reset advanced adapter properties.

Verify:

Wake on Magic Packet = Enabled

and:

Allow this device to wake the computer = Enabled

where those settings exist.

Problem 6 — Wake-on-LAN Option Is Missing

Possible reasons include:

• NIC doesn't support WoL
• generic/basic driver installed
• manufacturer driver missing
• Wi-Fi adapter doesn't support WoWLAN
• BIOS feature unavailable
• Modern Standby changes the exposed controls
• USB Ethernet adapter lacks appropriate wake support

Install the correct OEM/NIC driver before assuming the hardware is defective.

Advantages and Limitations of Wake-on-LAN

Wake-on-LAN vs Remote Desktop

These technologies perform different jobs.

They can complement each other:

WoL → PC wakes → Windows becomes available → RDP connection

Wake-on-LAN vs Remote Power Management Technologies

Enterprise servers often provide more advanced out-of-band management technologies.

Examples include dedicated management controllers and vendor server-management platforms.

These can provide capabilities beyond WoL, such as:

• power on
• power off
• reboot
• remote console
• BIOS access
• hardware monitoring
• remote installation

WoL is much simpler.

For ordinary desktop PCs, that simplicity is often an advantage.

Common Wake-on-LAN Mistakes

Mistake 1 — Assuming Windows Setting Alone Is Enough

WoL involves:

NIC + driver + OS + firmware + motherboard + network

All must cooperate.

Mistake 2 — Testing with Power Cable Removed

No standby electricity means no NIC listening for Magic Packets.

Mistake 3 — Using the Wrong MAC Address

Computers may have several MAC addresses:

• Ethernet
• Wi-Fi
• VPN adapter
• virtual adapter
• docking-station Ethernet

Use the MAC address of the interface that actually supports the desired wake mechanism.

Mistake 4 — Treating WoL as Authentication

A Magic Packet is not equivalent to a password.

Mistake 5 — Immediately Opening Router Ports

For Internet-based remote access, use secure architecture such as a VPN or authenticated management service rather than unnecessarily exposing broadcast/WoL mechanisms.

When Should You Use Wake-on-LAN?

WoL is particularly useful when:

• computers are remotely administered
• systems should sleep outside working hours
• overnight patching is required
• backups run outside business hours
• users remotely access office PCs
• IT staff manage many endpoints
• lab machines are only occasionally required

When Might You Disable Wake-on-LAN?

Consider disabling WoL when:

• the computer never needs remote wake
• unauthorized wakeups are occurring
• maximum standby-power reduction is important
• company security policy prohibits it
• the system is isolated or highly sensitive
• a laptop needs maximum battery preservation
• another secure out-of-band management technology is used instead

There is little benefit in leaving remote wake capabilities enabled on devices that will never use them.

Wake-on-LAN in Modern IT Environments

Wake-on-LAN is a good example of a technology that has survived because its underlying problem still exists.

The hardware has changed dramatically since the 1990s:

ISA/PCI NICs → onboard Ethernet → PCI Express → integrated controllers → Modern Standby devices

Operating systems and power-management technologies have also evolved.

Yet administrators still face the same question:

How can a computer save power while remaining remotely available when it is actually needed?

Wake-on-LAN remains one of the simplest answers.

Frequently Asked Questions

What is Wake-on-LAN?

Wake-on-LAN is a network power-management capability that allows a compatible computer to wake when its network interface detects a specified wake event, usually a Magic Packet.

What is a WoL Magic Packet?

A Magic Packet contains a synchronization sequence followed by 16 repetitions of the target NIC's MAC address. A compatible NIC can recognize this pattern while the computer is in a supported low-power state.

Who invented Wake-on-LAN?

Modern WoL is strongly associated with AMD's Magic Packet technology, co-developed with Hewlett-Packard in the mid-1990s. AMD published its Magic Packet white paper in November 1995. IBM, Intel, Microsoft and networking vendors subsequently played important roles in its wider adoption and integration.

Does Wake-on-LAN work when the computer is shut down?

It depends on the hardware, firmware and power state. Some systems can wake from an apparent shutdown because the firmware keeps the NIC armed. Microsoft does not officially define WoL from S5 as a Windows-supported wake scenario, although it acknowledges that some BIOS implementations can support it.

Can Wake-on-LAN turn on a PC after a power cut?

Not while the PC has no electricity. After electricity returns, motherboard settings such as Restore on AC Power Loss may determine what happens, but that is a separate feature from WoL.

Does WoL work over Wi-Fi?

Some systems support Wake on Wireless LAN (WoWLAN), but support depends on the wireless adapter, firmware, driver, operating system and power state.

Is Wake-on-LAN dangerous?

WoL itself normally only wakes a computer, but conventional Magic Packets do not provide strong modern authentication. The greater concern is unauthorized wakeups and the network services that become accessible after the computer starts.

Does Wake-on-LAN bypass my password?

No. Waking a computer does not normally bypass Windows, RDP, domain or application authentication.

Do I need the computer's IP address?

The target MAC address is fundamental to the classic Magic Packet. IP addresses and broadcast addresses may still be needed by the sending application to deliver the packet across the network.

Which port does Wake-on-LAN use?

Many WoL applications use UDP port 7 or 9, but the classic Magic Packet mechanism itself is based on the recognizable payload and does not inherently depend on one mandatory UDP port.

Why does WoL work from Sleep but not Shut down?

Sleep, hibernation, Fast Startup and full shutdown are different power states. The NIC may remain armed in one state but not another.

Can I use Wake-on-LAN before connecting through RDP?

Yes. A common workflow is:

Send WoL packet → Wait for Windows to resume/start → Connect through RDP.

For remote Internet access, use a secure VPN or management gateway rather than exposing services unnecessarily.

Does Wake-on-LAN increase electricity consumption?

WoL requires some standby power for the wake-capable hardware. However, it can enable much larger energy savings by allowing the rest of the PC to sleep instead of remaining fully operational solely for remote accessibility.

Conclusion

Wake-on-LAN is a mature but still highly useful network power-management technology. Its roots go back to AMD and Hewlett-Packard's Magic Packet work in the 1990s, followed by broad adoption through companies including IBM and Intel.

Its operation is elegantly simple:

Computer sleeps → NIC remains wake-capable → Magic Packet arrives → NIC recognizes its MAC address → motherboard receives wake event → computer wakes.

For home users, it can make remote access more convenient. For IT administrators, it can be much more valuable: computers can remain asleep outside business hours yet be awakened for backups, updates, maintenance, inventory or remote support.

The main limitation is that WoL is a wake mechanism rather than a security mechanism. It should therefore be combined with proper network segmentation, firewall policies, VPN access and strong authentication—especially when remote wake functionality must cross networks.

Configured correctly, Wake-on-LAN provides an effective balance between remote manageability, convenience and energy efficiency without requiring PCs to remain fully powered 24 hours a day.