Jump to content

Recommended Posts

Posted
We have AB Tutor here and so far so good and I was wanting to use the network boot feature but not having much success. We have HP 8000SFF Pc's that in the Bios have Network Boot enabled but they don't respond to the remote boot command from within AB Tutor. Is there anything else I can check to see what's at fault or need to check?
Posted (edited)

How have you set up the groups? If you've added them by entering names manually or from AD, I don't think it will have captured the MAC address details.

 

I think you need to add them by right-clicking them in the view and using the "Group > Add to..." menu items. Of course, the machines need to all be on when you do it or it won't get the MAC...

Edited by AngryTechnician
Posted
Ah, that could very well be it! Makes sense anyway that it would need the mac address, thanks. Why dont they make that clear, would have set them up that way in the first place.
Posted
Do you have VLANs in your environment? If so you might find that your router isn't allowing the WOL packets to traverse the VLANs. One way to test would be to run Wireshark on the source server and on a PC in the same VLAN as the target - see if you see the packets in both :)
Posted (edited)
Just as newpersn said, check the Advanced options of the NIC card in Device Manager. We've got a load of HP's and have to turn it on on all of them after imaging. Annoyingly the setting doesn't survive the sysprep process. Edited by MrLudwig
Posted
We found the reg entries and pushed them out. I think abtutor updates its config xml using the system account. As long as thd dns record is up to date it should send the packet to the correct mac and ip. If you check xml you should be able to find out if its up to date. You can also add other subnets to abtutor.
Posted
In the Dell BIOS you need to turn off low power in the power management settings for wol to work. We also had issues with our HP switches as they would not allow the packet to go over vlans. We tried some of the other settings in AB but they seemed to not work.
Posted (edited)
In the Dell BIOS you need to turn off low power in the power management settings for wol to work. We also had issues with our HP switches as they would not allow the packet to go over vlans. We tried some of the other settings in AB but they seemed to not work.

 

You should be able to WOL across VLANs on procurves using these... http://silvertrip-it.blogspot.co.uk/2012/10/how-to-setup-wake-on-lan-with-vlans-and.html

Edited by IrritableTech
  • Thanks 1
Posted

We have all of our PC's enabled in BIOS for WOL.... to wake up machines we log in to PfSense and wake up which ever ones need to awoken.

 

- - - Updated - - -

 

We have all of our PC's enabled in BIOS for WOL.... to wake up machines we log in to PfSense and wake up which ever ones need to awoken.

Posted (edited)
Well, ticked all settings in device manager, checked in bios and still nothing.

 

Bios upto date?

Network driver ok?

Power saving turned off within the drive?

What's the motherboards and nic in these?

Edited by newpersn
Posted

Check the address your broadcasting to, I struggled figuring that one out on our network. It will be the last address in the subnet range x.x.x.255

 

I tested by using wake on lan monitor on the pc i wanted to wake, then sending wol packets from my laptop, I was doing it via powershell script i found.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...