WOL relies on the NIC to do the wake, and in a VM you have virtual NICs not physical ones. If on the other hand they are Virtual Machines, then you have a problem. If the machine is a Physical machine, then you first configure it's BIOS to allow wake-on-lan and just send it a WakeOnLan packet, using any other software (there are many free ones) and then separately RDP to it. Open Services from Administrative Tools in Control Panel, scroll down to the service,Įnsure the service is started and that its Startup Type is set to Automatic so that it will run with Windows. Start Service 'Simple TCP/IP Service' (enables ports 7 & 9) Open Programs and Features from the Control Panel, click 'Turn Windows features on or off' on the sidebar, scroll down and check 'Simple TCPIP services', then click OK to install the feature. Install Windows Feature 'Simple TCPIP services' Mentioned in some sources, but possibly unneeded: Or its matching Graphical Interface found here. Many such are available on the Internet, by command line like wolcmd UDP is a broadcast packet which can always be received by your NIC, whereas TCP requires the computer to be powered up. Only UDP is needed, but you can if you wish open the TCP port as well. Open Windows Firewall from Control Panel. Right-click and open Properties then go to the Advanced tab andĮnable 'Wake on Magic Packet' or something similar. Open Device Manager from the Control Panel, expand Network Adapters and find your Ethernet Card.

However, if no such option is found in the BIOS, it might be safe to assume that it will work by default.

The actual method depends on your motherboard.

Your OS must be configured to enable Wake-on-LAN.

Your router must be configured to forward broadcast packets.

Your power supply must support Wake-on-LAN.

Your network card must support Wake-on-LAN.

The first step is to check the hardware : You will need to first use Wake-On-Lan to wake up the sleeping computer, Remote Desktop does not have any built-in remote wake-up capability.

Magic desktop 8