Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

WoL for Large Network?

Updated: 06 Sep 2011 | 5 comments
Guiedo's picture
+1 1 Vote
Login to vote
This issue has been solved. See solution.

I am trying to find a way to use WoL(Wake On Lan) for our network. Currently we have Broadcasting turned off and even with Altiris' check box it will not work.

Does anyone know how to get WoL to work for networks with over 6000 nodes?

Please let me know if there is anyway I can work around the broadcasting being turned off.

Comments

Palvaran's picture
23
Apr
2009
0 Votes 0
Login to vote

Wake on Lan (WoL) and the Altiris Deployment Console

To get WoL successfully working in Altiris, a few settings need to be changed.

1. Make sure that the BIOS is configured for Wake On Lan. Typically, you can find this under the network related section of your BIOS.

2. Make sure that Windows is configured for Wake On Lan. Typically, you can find this under the Device Manager, Network Adaptors. Find the NIC, such as Intel 82xxx or Broadcom 57xx and go to the properties of the device. Under the advanced tab, make sure that "Wake on link settings" is set to "forced" and "Wake on Settings" is set to "Magic & Direct".

3. Find a computer on a similar subnet and set it as a proxy server. For example, to wake up a machine with the IP address of 10.64.48.100, find another computer with an IP address in the 10.64.48.XX range and inside the Altiris Deployment Console, right click the computer and choose "Change Agent Settings" and then "Production Agent". Underneath the Proxy Tab, Checkmark "Forward Wake On Lan Packets".

From there, give Altiris one minute to restart the Altiris Agent and then go back to your computer that you wanted to wake up, in this case, 10.64.48.100. Simply right click the computer from inside of Altiris and choose "Power Control" and then "Wake up".

Your computer should now wake up when powered off and allow you to do any maintenance necessary!

Keep in mind, all of this is provided that networking has properly configured your switches to forward packets.

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

Guiedo's picture
23
Apr
2009
0 Votes 0
Login to vote

Is this still a broadcast? If

Is this still a broadcast? If so it will not work, that is turned off on our network. 

Thank you for your help, We have the first 3 set. Just trying to find workaround for non-Broadcasting.

jharings's picture
25
Apr
2009
0 Votes 0
Login to vote

It is multicast packet traffic

therefore it is a broadcast by default. What if you only allow a specific address range, which can be configured in the agent settings?

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Brandon's picture
27
Apr
2009
0 Votes 0
Login to vote

You are saying directed

You are saying directed broadcasts aren't allowed across the subnets right? You can still do a broadcast when the source and dest are on the same subnet? Test a machine on the same subnet as your PC with a 3rd party utlity. http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx . if that works, WOL Proxies are your answer.

Al Dullum's picture
28
May
2009
0 Votes 0
Login to vote

On Cisco gear this is the code

Example:
with Your Vlan as 100 and 16 bit subnet ( 255.255.0.0)
and your altiris server's ip as 10.10.0.10
This is for cisco not sure what any other vendor's code would look like.
Now you can wake on Lan and image across that Vlan\Subnet

interface Vlan 100
ip address 10.100.0.2 255.255.0.0
ip helper-address 10.10.0.10