How to Enable Wake-on-LAN Magic Packet on Windows (2026)

Managing a remote server or workstation becomes much simpler when you can power it on from anywhere. Wake-on-LAN (WoL) lets you wake a sleeping computer over the network by sending a special signal called a magic packet—no physical access required.

A magic packet is a broadcast frame containing 6 bytes of 0xFF followed by 16 repetitions of your computer’s MAC address. When your network card receives this specific pattern, it signals the motherboard to power on. This capability is invaluable for VPS administrators, IT professionals managing remote infrastructure, and anyone running home labs or development servers.

This guide walks you through the complete Wake-on-LAN setup process on Windows 10, 11, Server 2019, and Server 2022—from BIOS configuration through testing and security hardening.

How to Enable Wake-on-LAN on Windows

To enable Wake-on-LAN with magic packets on Windows:

Enable Wake-on-LAN in your computer’s BIOS/UEFI settings
Configure Windows network adapter Power Management to allow magic packet wake
Create Windows Firewall rule for UDP ports 7 and 9
Find your computer’s MAC address using ipconfig /all
Send a magic packet using PowerShell or a WoL tool to test

What You Need Before Starting

Hardware Requirements

Wake-on-LAN requires specific hardware capabilities:

Motherboard with WoL support — Most motherboards manufactured after 2010 include WoL functionality. Check your BIOS settings for Wake-on-LAN or PME (Power Management Event) options to confirm support.
Network card with WoL capability — Modern network interface cards (NICs) from Intel, Realtek, and other major manufacturers support WoL by default. Look for “Wake-on-LAN” in your adapter’s advanced properties.
Physical network connection — WoL requires a wired Ethernet connection. Wi-Fi adapters typically don’t support WoL because they power down completely in sleep mode.
Power supply that maintains standby power — Your power supply must provide standby power to the network card when the computer is in S3 (sleep) or S4 (hibernate) states.

Software & Network Requirements

Beyond hardware, you’ll need:

Windows administrative privileges — Changing adapter settings and creating firewall rules requires local administrator rights.
Static IP or reserved DHCP lease (recommended) — While not strictly required, a consistent IP address makes remote Wake-on-LAN more reliable.
Network access from sender device — For basic WoL, both computers must be on the same local subnet. Remote WoL requires additional configuration.
For VPS/dedicated servers — Verify your hosting provider supports Wake-on-LAN. Most providers disable this feature for security reasons and instead offer IPMI (Intelligent Platform Management Interface) or similar out-of-band management tools.

Important Limitations to Understand

Before proceeding, understand these WoL constraints:

Magic packets aren’t routable — By default, WoL only works within the same LAN. Sending magic packets across the internet requires port forwarding or VPN configuration.
Won’t work from complete shutdown — WoL requires the computer to be in a sleep or standby state (S3/S4), not fully powered off (S5). The network card needs standby power to listen for magic packets.
Different BIOS implementations use different terminology — Motherboard manufacturers use various names for WoL settings: “Wake on LAN,” “PME Event Wake Up,” “Power On By PCI-E,” or “Resume By PCI-E Device.”

Step 1 — Enable Wake-on-LAN in BIOS/UEFI

Accessing BIOS Settings

To enter your computer’s BIOS or UEFI firmware interface, restart the computer and press the appropriate key during the boot sequence:

Dell, Lenovo, HP: F2
ASUS, ASRock, MSI: Delete or F2
Gigabyte: Delete
UEFI systems: Hold Shift while clicking Restart in Windows, then navigate to Troubleshoot → Advanced Options → UEFI Firmware Settings

The exact key depends on your motherboard manufacturer. Watch for the “Press [KEY] to enter SETUP” message during boot.

Finding WoL Settings

Once in BIOS, navigate to the power management section. Common menu locations include:

Power Management
Advanced → APM Configuration
Integrated Peripherals
Advanced → Power Management Setup

Look for settings named:

Wake on LAN
PME Event Wake Up
Power On By PCI-E / PCI Device
Resume By PCI-E Device
Wake on PCI PME
EuP (Energy-using Products) 2013 — disable this if enabled, as it prevents WoL

Enable all WoL-related options you find. Some motherboards have multiple settings that must all be enabled for WoL to function.

Additional Power Settings

Some BIOS configurations include additional settings that affect Wake-on-LAN:

Deep Sleep States (S4/S5 support) — Enable S4 (hibernate) and optionally S5 (soft off) depending on how deeply you want the computer to sleep while maintaining WoL capability.
ERP (Energy-Related Products) compliance — This energy-saving standard can disable WoL. Set to “Disabled” or “S4+S5” rather than “S4 only” if you need WoL from deeper sleep states.
Fast Startup interaction — Some motherboards have a “Fast Boot” option that can interfere with WoL detection. If WoL doesn’t work after setup, try disabling Fast Boot in BIOS.

Save & Exit

After enabling all WoL settings, save changes and exit BIOS. The computer will restart with WoL hardware support active.

Step 2 — Configure Windows Network Adapter for WoL

Method 1 — Using Device Manager (GUI)

The graphical method works well for single-computer configuration:

Press Windows + X and select Device Manager
Expand Network adapters
Right-click your active Ethernet adapter (e.g., “Intel(R) Ethernet Connection”) and select Properties
Click the Power Management tab
Check these options:
- ✓ Allow this device to wake the computer
- ✓ Only allow a magic packet to wake the computer
Click the Advanced tab
Scroll through properties and locate:
- Wake on Magic Packet — Set to Enabled
- Wake on pattern match — Set to Disabled (optional, for security)
- WOL & Shutdown Link Speed — Set to Not Speed Down or 10 Mbps First
Click OK to save changes

The specific property names vary by network card manufacturer. Intel adapters typically list “Wake on Magic Packet” explicitly, while Realtek adapters may call it “WakeUp Capabilities.”

Method 2 — Using PowerShell (Command Line)

For remote servers or scripting multiple machines, use PowerShell:

# Verify current WoL status
Get-NetAdapter | Select Name, InterfaceDescription
Get-NetAdapterPowerManagement -Name "Ethernet"

# Enable WoL
Enable-NetAdapterPowerManagement -Name "Ethernet" -WakeOnMagicPacket

# Verify change
Get-NetAdapterPowerManagement -Name "Ethernet" | Select WakeOnMagicPacket

Replace “Ethernet” with your adapter’s actual name from the first command’s output. Common names include “Ethernet,” “Ethernet0,” or “Local Area Connection.”

The PowerShell networking cmdlets provide programmatic control over adapter settings—useful when configuring multiple servers.

Windows Fast Startup Consideration

Windows Fast Startup (a hybrid shutdown mode) can prevent Wake-on-LAN from working properly. Fast Startup doesn’t fully initialize network hardware on boot.

To disable Fast Startup:

Open Control Panel → Power Options
Click Choose what the power buttons do (left sidebar)
Click Change settings that are currently unavailable
Uncheck Turn on fast startup (recommended)
Click Save changes

Trade-off: Disabling Fast Startup adds 5-10 seconds to your boot time but ensures WoL compatibility.

Step 3 — Find Your Computer’s MAC Address

Every network adapter has a unique Media Access Control (MAC) address that identifies it on the network. Magic packets target this address.

Method 1 — Command Prompt

ipconfig /all

Locate the “Physical Address” field under your active Ethernet adapter. It appears in the format XX-XX-XX-XX-XX-XX (e.g., 00-1A-2B-3C-4D-5E).

Method 2 — PowerShell

Get-NetAdapter | Select Name, MacAddress

This displays all network adapters with their MAC addresses in a clean table format.

Method 3 — Device Manager

Open Device Manager → Network adapters
Right-click your adapter → Properties → Advanced tab
Look for “Network Address” or “Locally Administered Address”

Some adapters display the MAC address here, though it may be labeled as “Not Present” if not manually configured.

Note the MAC Address Format

Different WoL tools accept MAC addresses in various formats:

00-1A-2B-3C-4D-5E (Windows default, hyphen-separated)
00:1A:2B:3C:4D:5E (colon-separated, common in Linux/Mac tools)
001A2B3C4D5E (no separators)

Most WoL applications auto-detect the format, but keep this in mind when entering the address manually.

Step 4 — Configure Firewall Rules (Critical for Windows Firewall)

Understanding WoL and Firewalls

Magic packets are typically sent via UDP (User Datagram Protocol) on port 7 or port 9. According to IETF standards, port 7 is the “Echo” protocol port, while port 9 is the “Discard” protocol port—both historically used for WoL implementations.

Windows Defender Firewall blocks inbound UDP traffic by default, which will prevent magic packets from reaching your network adapter.

Creating Inbound Firewall Rule (GUI)

Press Windows + R, type wf.msc, and press Enter to open Windows Defender Firewall with Advanced Security
Click Inbound Rules in the left pane
Click New Rule in the right pane (Actions)
Select Port → Next
Select UDP and enter Specific local ports: 7,9 → Next
Select Allow the connection → Next
Check all profiles: Domain, Private, Public → Next
Name the rule: Wake-on-LAN Magic Packet → Finish

This rule allows inbound UDP traffic on ports 7 and 9 from any source—sufficient for local network WoL.

PowerShell Method

New-NetFirewallRule -DisplayName "Wake-on-LAN" -Direction Inbound -Protocol UDP -LocalPort 7,9 -Action Allow

This single command creates the same rule as the GUI method. The New-NetFirewallRule cmdlet documentation provides additional parameters for restricting source IPs or profiles.

Third-party Firewall Considerations

If you use a third-party firewall (Norton, McAfee, ZoneAlarm, etc.), create a similar inbound rule allowing UDP ports 7 and 9. Consult your firewall’s documentation for specific steps.

Step 5 — Send a Magic Packet to Test WoL

Option 1 — Built-in Windows PowerShell Script

This PowerShell function sends a magic packet without requiring third-party software:

# Function to send magic packet
function Send-WOL {
    param(
        [string]$MacAddress,
        [string]$BroadcastAddress = "255.255.255.255",
        [int]$Port = 9
    )

    # Remove separators and convert to byte array
    $Mac = $MacAddress -replace '[:-]',''
    $MacBytes = 0,2,4,6,8,10 | % { [Convert]::ToByte($Mac.Substring($_,2), 16) }

    # Build magic packet (6×FF + 16×MAC)
    $Packet = [byte[]](,0xFF * 6) + ($MacBytes * 16)

    # Send packet
    $UdpClient = New-Object System.Net.Sockets.UdpClient
    $UdpClient.Connect($BroadcastAddress, $Port)
    [void]$UdpClient.Send($Packet, $Packet.Length)
    $UdpClient.Close()

    Write-Host "Magic packet sent to $MacAddress"
}

# Usage example
Send-WOL -MacAddress "00-1A-2B-3C-4D-5E"

The magic packet structure is precisely defined: 6 bytes of 0xFF (255 in decimal) followed by the target MAC address repeated 16 times, totaling 102 bytes. This magic packet specification is recognized by all WoL-compliant network cards.

You can customize the broadcast address (for subnet-specific broadcasting) or port (if using non-standard WoL ports).

Option 2 — Third-Party Tools

Several free tools simplify magic packet sending:

Tool	Platform	GUI	Script Support	Cost
PowerShell (native)	Windows	No	Yes	Free
WakeMeOnLan	Windows	Yes	No	Free
Depicus WOL GUI	Windows, Mac	Yes	Limited	Free
Fing mobile app	iOS/Android	Yes	No	Free (with ads)

WakeMeOnLan (by NirSoft) is particularly user-friendly—it scans your network for devices, displays their MAC addresses, and sends magic packets with a single click.

Depicus Wake On Lan GUI offers cross-platform support and can save MAC addresses for repeated use.

Fing is ideal for mobile scenarios—wake your home server from your phone before connecting via VPN.

Testing the Setup

Put the target computer to Sleep (Start → Power → Sleep). Don’t shut down completely—WoL requires the computer to be in a sleep state.
From another computer on the same network, send a magic packet using PowerShell or one of the tools above
The target computer should wake within 2-10 seconds (varies by motherboard)
If it wakes successfully, check Event Viewer (Windows Logs → System) and filter for “Power-Troubleshooter” events to confirm the network adapter triggered the wake event

Wake-on-LAN for Remote/Internet Access (Advanced)

The Routing Challenge

Magic packets use broadcast traffic, which routers don’t forward by default. This limitation prevents WoL from working across the internet without additional configuration.

Three solutions enable remote Wake-on-LAN:

Solution 1 — Port Forwarding on Router

Configure your router to forward UDP port 7 or 9 to the target computer’s static IP address:

Log into your router’s admin interface (typically 192.168.1.1 or 192.168.0.1)
Navigate to Port Forwarding or Virtual Server settings
Create a new rule:
- External port: 9
- Internal IP: Your computer’s static IP (e.g., 192.168.1.100)
- Internal port: 9
- Protocol: UDP
Save the rule

To send a magic packet from the internet, use your public IP address as the destination instead of the broadcast address.

Security Warning: Port forwarding exposes your WoL service to the internet. Anyone who discovers your public IP and MAC address can wake your computer. See the Security Considerations section below for hardening steps.

Solution 2 — VPN Connection

A more secure approach uses a VPN tunnel:

Set up a VPN server on your local network (or use a router with built-in VPN capabilities)
Connect to the VPN from the remote location
Send the magic packet over the VPN tunnel using the local broadcast address (255.255.255.255 or your subnet’s broadcast address like 192.168.1.255)

This approach treats your remote device as if it’s on the local network—no port forwarding required and significantly more secure.

Solution 3 — Subnet-Directed Broadcast

Some routers support directed broadcasts to specific subnets:

Enable directed broadcast forwarding in your router (often disabled by default for security)
Send the magic packet to your subnet’s broadcast address (e.g., 192.168.1.255) instead of 255.255.255.255
The router forwards the packet to all devices on that subnet

Check your router’s documentation—many consumer routers block directed broadcasts as a security measure.

For VPS/Dedicated Server Users

Most hosting providers disable Wake-on-LAN for security and infrastructure management reasons. Data centers typically use out-of-band management interfaces instead:

IPMI (Intelligent Platform Management Interface) — Industry-standard remote management
iLO (HP), iDRAC (Dell), IMM (Lenovo) — Vendor-specific implementations

Check your provider’s documentation or contact support before attempting WoL configuration. For example, Hostifire’s dedicated servers starting at $69.90/mo typically include remote management capabilities—confirm the specific method with the support team rather than assuming WoL availability.

Troubleshooting Common Wake-on-LAN Issues

Issue 1 — Computer Doesn’t Wake

Work through this checklist systematically:

[ ] BIOS WoL setting enabled? Re-enter BIOS and verify all WoL/PME options are enabled
[ ] Network adapter Power Management settings correct? Check Device Manager → adapter properties → Power Management tab
[ ] Computer in sleep mode, not shutdown? WoL requires sleep/standby (S3/S4), not full shutdown (S5)
[ ] Magic packet sent to correct MAC address? Verify with ipconfig /all — ensure no typos
[ ] Firewall rule created? Check Windows Firewall → Inbound Rules for the WoL rule
[ ] Fast Startup disabled? Control Panel → Power Options → disable Fast Startup
[ ] Physical Ethernet connection? WoL doesn’t work over Wi-Fi on most hardware

Issue 2 — Works Locally But Not Remotely

If WoL functions on the local network but fails from the internet:

Verify router port forwarding configuration — Ensure UDP port 7 or 9 forwards to the target computer’s static IP
Check if router blocks broadcast packets — Some routers filter broadcast traffic even with port forwarding enabled
Confirm external IP address — Your public IP may change if you don’t have a static IP from your ISP. Use a dynamic DNS service.
Test with VPN first — This eliminates router configuration variables and confirms the computer’s WoL setup works

Issue 3 — Network Adapter Loses Settings After Reboot

Persistent driver or hardware issues may reset WoL settings:

Update NIC driver — Download the latest driver directly from the manufacturer (Intel, Realtek, etc.), not Windows Update
Prevent Windows Update from overriding drivers — Set Group Policy: Computer Configuration → Administrative Templates → Windows Components → Windows Update → “Do not include drivers with Windows Updates” → Enabled
Check for BIOS reset — If BIOS settings revert, replace the CMOS battery (especially on older motherboards)

Issue 4 — WoL Works But Computer Wakes Randomly

Unwanted wake events disrupt energy-saving goals:

Disable broader wake options — In adapter properties → Power Management, ensure “Only allow a magic packet to wake the computer” is checked (not just “Allow this device to wake the computer”)
Check for scheduled tasks — Windows Task Scheduler may have tasks configured to wake the computer. Review Task Scheduler Library → look for “Wake the computer to run this task” checkbox
Review Event Viewer wake sources — Event Viewer → Windows Logs → System → Filter current log → Event ID 1 (Power-Troubleshooter) reveals what triggered each wake event

Flowchart Summary

Computer doesn't wake?
├─ In sleep mode? → No → Put to sleep, try again
├─ BIOS WoL enabled? → No → Enable in BIOS
├─ Windows adapter settings? → No → Configure Power Management
├─ Correct MAC address? → No → Verify with ipconfig /all
├─ Firewall blocking? → No → Create UDP 7,9 inbound rule
└─ Still failing? → Check NIC driver updates or hardware compatibility

Security Considerations for Wake-on-LAN

Risks of WoL Over Internet

Wake-on-LAN has inherent security limitations:

Unauthenticated protocol — Magic packets contain no authentication mechanism. Anyone with your MAC address can wake your computer.
Port forwarding exposure — Opening UDP ports 7 or 9 to the internet exposes your network to scanning and potential attacks.
Denial-of-service potential — Attackers can repeatedly wake your computer, preventing it from entering sleep mode and increasing electricity costs.

Best Practices for Secure WoL

Use VPN instead of port forwarding — Require VPN authentication before accessing the local network to send WoL packets. This adds a strong authentication layer.
Change default WoL port — Configure your WoL tool and firewall to use a non-standard port (e.g., 12345) instead of the well-known ports 7 or 9. This defeats automated scanners.
Implement SecureOn passwords — Some network cards support password-protected WoL. Check your adapter’s Advanced properties in Device Manager for “SecureOn” or “Magic Packet Password” options.
Limit firewall rules to specific source IPs — Rather than allowing UDP from any source, restrict the firewall rule to your known external IP addresses if they’re static.
Monitor wake events — Regularly review Event Viewer (Windows Logs → System → filter for Power-Troubleshooter events) to detect unauthorized wake attempts.
Disable WoL when not needed — If you only need remote access occasionally, disable WoL in BIOS/adapter settings when not actively using it.

Security best practices recommend implementing defense-in-depth strategies—combining multiple security controls rather than relying on a single measure.

For VPS/Dedicated Servers

Hosting providers typically disable WoL to prevent security issues and abuse:

Consult provider security policies — Enabling WoL may violate terms of service or security best practices
Use IPMI/iLO/iDRAC instead — These out-of-band management interfaces provide authenticated, encrypted remote power control
If WoL is required — Coordinate with the provider’s security team to implement compensating controls (VPN requirement, firewall restrictions, etc.)

For comprehensive server security beyond WoL, see our guide on how to secure your VPS server.

Network Segmentation

For enterprise environments:

Isolate WoL-enabled devices on a separate VLAN — Network segmentation limits the blast radius if WoL is exploited
Use firewall rules to restrict WoL senders — Only allow specific devices (e.g., admin workstations) to send magic packets

Use Cases for Wake-on-LAN in Server Management

Remote VPS/Dedicated Server Management

Wake-on-LAN enables cost-effective server resource management:

On-demand development/staging servers — Wake servers only during business hours or active development, reducing hosting costs for underutilized environments
Batch processing workflows — Power on compute resources for scheduled jobs (data processing, backups, batch analytics), then return to sleep when idle
Note on VPS provider support — Most VPS providers don’t support WoL. If you’re considering upgrading from shared hosting to VPS, verify WoL support with the provider or use their web-based console for power management instead.

Home Lab & Development Environments

Developers and IT professionals benefit from flexible home lab power management:

Wake test servers for development work — Keep lab infrastructure powered off until needed, then wake remotely when starting development sessions
Energy-efficient homelab operations — Reduce electricity costs by running servers only when actively used (particularly beneficial for power-hungry dedicated servers)

IT Administration Scenarios

Enterprise IT departments leverage WoL for maintenance windows:

Midnight patching and updates — Wake all workstations, apply Windows Updates or security patches, then return machines to sleep
Scheduled backup operations — Wake servers for backup jobs, execute backups, verify completion, then sleep
Remote support sessions — Wake a user’s computer for troubleshooting without requiring the user to be present or leave the machine powered on

When NOT to Use WoL

Wake-on-LAN isn’t appropriate for every scenario:

Production servers requiring 24/7 uptime — Critical services should remain powered on with proper redundancy, not depend on WoL
Security-critical systems — The unauthenticated nature of WoL creates risk for high-security environments
Wi-Fi-only devices — WoL requires wired Ethernet connections in most implementations
Public cloud instances — Cloud VPS instances from AWS, Azure, Google Cloud, DigitalOcean, etc., don’t support WoL—use the provider’s API or console instead

Frequently Asked Questions

Q1: What is a magic packet in Wake-on-LAN?

A magic packet is a broadcast frame containing 6 bytes of 0xFF followed by 16 repetitions of the target computer’s MAC address. It’s sent over the network to wake a sleeping computer. The specific pattern (102 bytes total) is recognized by WoL-enabled network cards.

Q2: Does Wake-on-LAN work over Wi-Fi?

Most implementations don’t support WoL over Wi-Fi. WoL requires a wired Ethernet connection because the network adapter must remain powered in sleep mode, which Wi-Fi adapters typically don’t support. Some newer Wi-Fi 6 adapters claim WoL support, but it’s unreliable compared to Ethernet.

Q3: Can I use Wake-on-LAN over the internet?

Yes, but it requires router configuration (port forwarding UDP 7 or 9) or a VPN connection. For security, VPN is strongly recommended over port forwarding. The magic packet must reach your local network before it can wake the target computer.

Q4: What’s the difference between WoL and remote desktop?

Wake-on-LAN turns on a sleeping computer. Remote Desktop (RDP) connects to an already-running computer for remote control. You’d use WoL first to wake the computer, then use Windows RDP hosting to connect and control it. Hostifire offers affordable Windows RDP hosting starting at $4.99/mo for remote access needs.

Q5: Does Wake-on-LAN work if the computer is fully shut down?

No. WoL requires the computer to be in a sleep or standby state (S3 or S4 power state), not a complete shutdown (S5). The network card needs standby power to listen for magic packets. If fully powered off, the NIC has no power and can’t detect incoming packets.

Q6: Which port does Wake-on-LAN use?

Wake-on-LAN typically uses UDP port 7 or 9. Port 7 (Echo protocol) and port 9 (Discard protocol) are the historical standards. Some implementations allow custom ports for added security—just ensure the sender and firewall configuration match.

Q7: Why isn’t Wake-on-LAN working on my VPS or dedicated server?

Most hosting providers disable WoL for security reasons and infrastructure management constraints. Check your provider’s documentation or contact support. Use IPMI, iLO, iDRAC, or the provider’s web-based control panel for remote power management instead. Hostifire’s dedicated servers include remote management capabilities—contact support to confirm the specific power control method available for your server.

Q8: Can Wake-on-LAN drain my electricity bill?

WoL requires minimal standby power—typically 1-5 watts to keep the network card listening for magic packets. This is negligible compared to a fully running computer (50-300 watts depending on configuration). The energy cost is approximately $1-5 per year at average U.S. electricity rates.

Conclusion

Wake-on-LAN provides powerful remote power management for Windows computers, enabling energy-efficient server administration, flexible home lab operations, and convenient remote access to workstations. By configuring BIOS settings, Windows network adapter properties, and firewall rules, you can wake sleeping computers from anywhere on your local network—or across the internet with proper security precautions.

Key takeaways: enable WoL in both BIOS and Windows adapter settings, create firewall rules for UDP ports 7 and 9, prioritize VPN over port forwarding for remote access, and monitor wake events for security. Remember that most VPS and dedicated server providers disable WoL in favor of more secure out-of-band management interfaces like IPMI.

If you need reliable remote server infrastructure with professional management capabilities, explore Hostifire’s affordable Cloud VPS hosting starting at $5.99/mo or dedicated servers starting at $69.90/mo with full remote management support. Both options include 24/7 technical support, a 99.99% uptime guarantee, and a 30-day money-back guarantee.

Sources

Microsoft Learn — PowerShell NetAdapter Module — Official documentation for PowerShell network adapter cmdlets used in this guide
Wireshark Wiki — Wake on LAN — Technical specification of magic packet structure (6×FF + 16×MAC)
NirSoft WakeMeOnLan Tool — Free Windows utility for sending magic packets
Depicus Wake On Lan GUI — Cross-platform WoL tool with graphical interface
IETF RFC 862 — Echo Protocol — Standard defining UDP port 7 used for WoL
NIST Cybersecurity Framework — Defense-in-depth security best practices referenced in Security Considerations section
Microsoft Learn — New-NetFirewallRule Cmdlet — PowerShell firewall configuration documentation

Schema Markup (FAQPage JSON-LD)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is a magic packet in Wake-on-LAN?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A magic packet is a broadcast frame containing 6 bytes of 0xFF followed by 16 repetitions of the target computer's MAC address. It's sent over the network to wake a sleeping computer. The specific pattern (102 bytes total) is recognized by WoL-enabled network cards."
      }
    },
    {
      "@type": "Question",
      "name": "Does Wake-on-LAN work over Wi-Fi?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most implementations don't support WoL over Wi-Fi. WoL requires a wired Ethernet connection because the network adapter must remain powered in sleep mode, which Wi-Fi adapters typically don't support."
      }
    },
    {
      "@type": "Question",
      "name": "Can I use Wake-on-LAN over the internet?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, but it requires router configuration (port forwarding UDP 7 or 9) or a VPN connection. For security, VPN is strongly recommended over port forwarding."
      }
    },
    {
      "@type": "Question",
      "name": "What's the difference between WoL and remote desktop?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Wake-on-LAN turns on a sleeping computer. Remote Desktop (RDP) connects to an already-running computer. You'd use WoL first to wake the computer, then RDP to control it."
      }
    },
    {
      "@type": "Question",
      "name": "Does Wake-on-LAN work if the computer is fully shut down?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. WoL requires the computer to be in a sleep or standby state (S3 or S4), not a complete shutdown (S5). The network card needs standby power to listen for magic packets."
      }
    },
    {
      "@type": "Question",
      "name": "Which port does Wake-on-LAN use?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Wake-on-LAN typically uses UDP port 7 or 9. Some implementations allow custom ports for added security."
      }
    },
    {
      "@type": "Question",
      "name": "Why isn't Wake-on-LAN working on my VPS or dedicated server?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most hosting providers disable WoL for security reasons. Check your provider's documentation or contact support. Use IPMI, iLO, or the provider's control panel for remote power management instead."
      }
    },
    {
      "@type": "Question",
      "name": "Can Wake-on-LAN drain my electricity bill?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "WoL requires minimal standby power (typically 1-5 watts) to keep the network card listening. This is negligible compared to a fully running computer (50-300 watts)."
      }
    }
  ]
}