Joseph Dupre

My mistake. Apparently Google directed me here, not your website. It was Windows's firewall that was blocking the incoming packets, so WOL Agent never got them, thus no broadcasts. Adding a rule to Windows firewall solved that. (I forgot that Wireshark taps in before the firewall, that's why I was confused to see the incoming unicast packet but not the outgoing broadcast.) All is good. Thanks for the cool tool.

Thanks for the reply. Your web site directed me to Source Forge for support. Is there a better forum? I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out. I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to...

Thanks for the reply. You web site directed me to Source Forge for support. Is there a better forum? I installed WOL Agent on Windows 7 Pro. I see that the service is running. With Wireshark I see the incoming packets from the internet that pass through my firewall to the WOL Agent machine. However, there are no broadcast WOL packets being sent out. I disabled the firewall, and now I see the broadcast packets. Enable the firewall, and broadcast packets do not get sent. How do I set up a rule to allow...

I am able to wake up a particular machine with the Wake On LAN tool on my LAN, so I know I have the BIOS and Windows 10 settings enabling WOL. Now I am trying to wake up the machine via the internet. Aparently my firewall does not allow port forwarding to a broadcast address, so I set up a rule to forward to the specific NAT address of the machine I want to wake up. When the machine is awake, and I have the "Listener" window open, when I send the WOL pakect over the internet it is displayed in the...