How to configure PC remote shutdown and wake-on-lan feature.



ATConsole Power Management FAQ

Can I use ATConsole Power Management in peer-to-peer network (not joined to domain)?

How to configure the Firewall on the local PC?

What protocols and ports does the program use

Program can't determine MAC address of remote PC

Wake-on-LAN Troubleshooting

Is it possible to wakeup (Wake-On-LAN) PC in a different subnet?


Can I use ATConsole Power Management in peer-to-peer network (not joined to domain)?

The easiest way to manage computers with ATConsole Power Management is to run the program in a Windows domain. This way, you will not need to make additional settings to the remote computer – all you have to do is obtain the domain administrator privileges. If your computer is not a member of a domain, you will need to provide an administrative user name and password on the program’s prompt for each remote computer.

How to configure the Firewall on the local PC?

The windows firewall may block sending the Wake-on-lan packets. To allow this, add the following app to the Firewall exceptions list: %ProgramFiles%\ATConsole\atconsole.exe.


What protocols and ports does the program use

Program uses SMB protocol, MICROSOFT_DC port (TCP 445) for shutdown, reboot, hibernate actions. In Wake-On-LAN mode, ATConsole uses UDP port 7 by default.


Program can't determine MAC address of remote PC

Ensure that the remote PC is accessible over network (powered on). To fetch the mac address the target PC should belong to the same subnet.


Wake-on-LAN Troubleshooting

  1. Check up firewall on the local PC, it may block sending the Wake-On-LAN packet.
  2. Whether MAC address has been correctly specified?
  3. Wake-on-LAN function should be enabled on the target PC. Use documentation of the motherboard and network adapter of the target PC.
  4. Use the Wake-on-LAN Packet sniffer to test whether the target PC is receiving wake-up packets.


Is it possible to wakeup (Wake-On-LAN) PC in a different subnet?

Default value of broadcast address (255.255.255.255) won't work across subnets. The wakeup packets are not addressed to the client specific IP address is because most routers will drop the client from their tables if the machine has been off for a period of time. Once that happens, explicitly addressed packets would be dropped at the router, but broadcasts to a specific segment will always get there. If all machines on subnet is down router will drop all packets.
For example, to send wakeup packet from IP 192.168.1.32 to IP 192.168.2.15 broadcast address value should be set to 192.168.2.255 (subnet mask 255.255.255.0).


Download Free 30-day trial