Sorry for the delay in responding. I also have a lot of gov machines and that can be a real problem if they won't update the GPO for you.
You can edit the database manually and accomplish this. The file is simple XML, and by default, it is located at C:\ProgramData\Aquila Technology\WakeOnLAN\machines.xml You will want to change Method to 1 for each machine. For example: <method>1</method>
The only thing I can think of is the account you are using for the scheduled task. Is it the same account you are logged in as? Does that account have authority to shutdown the remote computer?
I just realized how confusing this must be, there are a lot of options. So let's break this down to managable steps. First let's start with two machines, call them source and destination. You don't need to install any software on the destination, but just for testing, let's install WOL on both. That way you can run the listener on it to see if it's receiving packets. Send a wakeup command to the destination. Make sure the listener receives it. Then try actually waking it up from power off. For this...
The agent would be installed on a server that is always on. You only need one agent. Are you having trouble? To set this up, you need to test one step at a time. First make sure it works on a local network. Then try sending directly to the agent. Then try to the agent from outside your lan. Use the "listener" function to verify you are receiving wol packets.
You configure WOL to send the packets to the router outside address. Then you configure the router to forward port 9 to the host that has the Agent running on it. Then the agent will receive the packet and broadcast it for you. I have a simple diagram on the agent's webpage that may help.
I assume you mean 192.168.178.255, not .55? .55 is not a broadcast address. I need more information about what you are trying to do. I think you are saying you want to send WOL packets from the internet, outside of your LAN, to your router, forward them to a server running Agent, then to the local network. Is this correct? Your router would be configured to forward the port 9 packets directly to the server running agent. For example, 192.168.0.8. NOT a broadcast address. The router probably cannot...
I'm sorry I'm still thinking. The command line program and GUI both call the same exact DLL function. So it should work...