Wake on Lan Relay Agent DCm 3.0
SilenceBit
June 9th, 2009
I have installed a DCM 3.0 on my environment and pushed Altris Agent on my clients as well as DCM agent. I configured tghe Agent setting swith tickel enable as well. but i cannot get the Wake on Lan to work. i tried with changing Ports to 9 that didn;t help either. i read in Symantec Forums to use one of the agent as a relay agent or a proxy for the WOL packet to be sent, i tried diffrent palces but cannot find how to make a client a relay agent or Proxy for WOL packets.Any help will be Appreciated
Wake on Lan Relay Agent Dell DMC v3.0
I had this same issue at a previous client. I reported this to support and is now known as a feature request. Here is what I found out troubleshooting this and what I got back from support.
In 6.0 this was the scenario, all machines were considered a WoL proxy, the NS server would try a directed broadcast, 192.168.1.255 for example for a 192.168.1.0/24 subnet. If the machine did not wake up, the NS would forget the direct power on request and proxy. So it would then look to see which machines have recently checked in. It will then tell one of those machines to send out the WoL packet. This was pretty much 100% successful for me in the past. Besides the WoL auto proxying, you could also allow directed broadcasts from only the NS, if you wanted to implement this feature on the network side.
In 7.0, when you send a WoL packet to a machine, the NS server will send a broadcast (not even a directed one) to try and wake up the machine and that is it. So basically, it sends a WoL packet to 255.255.255.255. If this machine is not on the same subnet, the machine will never wake up, as no router should ever forward broadcasts. One thing I found, is if you put a Task Server on the same subnet as the client you are trying to wake up, and the task agent registers with that task server, once it is turned off. You can send a WoL packet and the NS will tell the Task Server to send it, so the 255.255.255.255 WoL packet will be on the correct subnet and would wake up the machine. However, this leads to having to have a Task Server (Site Server with Task Services) on every subnet. Also, sometimes the machine will not automatically pick that Task Server and when it doesnt WoL wont work again.
I was told they are looking to implement directed broadcasts in the future. They did not say much along the lines with the Agent proxing the request in the future.
Hope this helps,
David Ramazetti
Senior Technical Solutions Consultant
XCEND Group, Inc.
www.xcendgroup.com <http://www.xcendgroup.com/?signature>
Would you like to reply?
Login or Register to post your comment.