I'm in an environment with subnets and trying to get WOL to work with LDMS 9.0 SP2 using the WAKE UP option available on RIGHT-CLICK within the NETWORK VIEW.
I should preface by saying that my clients are setup to work with WOL and have done so for many years when I had a different management console residing on the same subnet. That is to say that if I use this OLD TOOL now, as it is still present and unchanged from the past, I can wake up my computers. So I know the clients are fine. In fact we retested this just to confirm the clients were all setup and they were.
Regarding the network, the LDMS core is on a different subnet from the client computers but that server has been configured as an IP Helper on the client subnets. Additionally, UDP ports 0 and 7 are set to forward from the LDMS Core to the subnets where the clients live. Yesterday my network admin tested WOL across the subnets using a SolarWinds WOL tool and Wireshark to see the traffic. The SW WOL tool was running on the LDMS core and Wireshark was on a client computer on a subnet. An adjacent computer was the target for WOL and when the WOL command was issued we observed the magic packet traffic via Wireshark and we observed the target machine wake up as it is supposed to do. Using LDMS 9.0 SP2 in that same scenario we were unable to wake up any machines.
It is worth noting that between the old client management software, the Solar Winds WOL tool, and LDMS 9.0, we observed traffic from all three whenever we issued WOL commands, however all three tools generated DIFFERENT packets. Said another way, the packet captures in Wireshark showed 3 distinct packet signatures such that we could do a blind test free of IP address and other external information and simply look at the packtes then be able to identify which tool they came from. And in the end the LDMS WOL packets did not do their job when the other two did.
-does anyone have any information that may help me figure out how to configure WOL to work in LDMS 9.0 SP2?
I thought this was something that just worked with default settings out of the box, but obviously I was wrong.
BTW, we were using UDP port 0 for WOL because that was default, but absent the desired effect we tested port 7 but got the same result...