A little scripting project on REDMOND to wake machine in the labs using Gammadyne Corporation’s WOL.EXE (v1.2). This is a fall back if other WOL tools fail.
The trick is that Packets cannot be broadcast across the Internet, only a LAN. To get around the subnet issues REDMOND needs to think that the VLAN is the subnet and hence although REDMOND’s actual netmask = 255.255.255.192 to make the VLAN the subnet we will need have the mask set as 255.255.255.0
>wol 001143a5949c Wake-On-LAN Utility 1.1 Copyright (C) 2000-2003 By Greg Wittmeyer All Rights Reserved Wake-up packet sent successfully
WOL.exe sends a “Wake On LAN” packet to the NIC with the matching Ethernet Address (EA). The script is pretty crude, as there is just a list of the EAs by subnet … I am testing the theory first – pretty can come later *chuckle*
Things went well for DM109, DM204, DM208 and DM211. Not so well for the DELL GX280′s in AH222 … a bit more testing and it appears not to be a subnet related issue. Something is rotten in the land of AH222 as even locally in the lab you cannot WOL the buggers
Fig1. Properties tab with ‘both’ enabled
Even if the WOL is enabled via the properties tab on the NIC (WinXP), it also needs to be enabled via BIOS.
BIOS |---Power Management |---Remote Wake Up [ON]
After these are changed for AH222 things should be ok And on a test GX280 things look OK
Fig2.Magic packet on port 12287
The next thing is to find out what other services I may have broken with the change of netmask … tomorrows project
 WOL.EXE [Gammadyne Corporation]