6Foot2 Posted April 16, 2015 Posted April 16, 2015 We have quite a few of these now and so we wanted to enable WOL for all of them to have them ready for users when they come in [Deploy any new packages and complete any waiting updates etc] We found that none of the 9020s would WOL. I have updated the BIOs from A02 to A10 and checked the BIOS settings again [Power management: WOL: LAN only, Deep sleep control: Disabled] The BIOS upgrade did not resolve the issue. I called Dell who are now escalating this to their Product Team [?] Waiting for more news...
southhamster Posted April 16, 2015 Posted April 16, 2015 We have some old intel based fujitsu PC's with this problem. Turned out to be a setting in the LAN in windows. I didnt believe it at first until I saw it with my own eyes. I think it was to do with power but cant remember exactly. 1
Steve21 Posted April 16, 2015 Posted April 16, 2015 Did you change the power state from S5 to S3 thingy within the BIOS? (Can't remember if that is deep sleep or not) Steve 1
NB9457 Posted April 16, 2015 Posted April 16, 2015 We have some old intel based fujitsu PC's with this problem. Turned out to be a setting in the LAN in windows. I didnt believe it at first until I saw it with my own eyes. I think it was to do with power but cant remember exactly. That^ I've the same issue with Fujutsu and RM machines. Had to install the intel LAN driver and facility then manually configure it on each machine. Was quite a tax and I was annoyed I couldn't do it from BIOS, but it worked! 1
6Foot2 Posted April 16, 2015 Author Posted April 16, 2015 I have just been to have a look at one of the classroom machines to check the network card settings in Windows: http://i.snag.gy/V9WMy.jpg http://i.snag.gy/SYYky.jpg I should have thought that these settings would be OK? Looking at if there are any updated Intel drivers now...
newpersn Posted April 16, 2015 Posted April 16, 2015 Allow only a magic packet to wake the computer need to be ticked. 1
MrEprise Posted April 16, 2015 Posted April 16, 2015 We had a similar issue with some of our HP desktop models with Intel network adapters where by WOL stopped working the moment I updated the drivers to ones from the Intel website, but fixed again once I reverted to drivers available from Windows Update. I guess there's a setting (hidden?) somewhere either in Intel's driver settings or in their management software but I was too lazy to find this out as since the windows update drivers worked fine, there wasn't any point. 1
Sagima Posted April 16, 2015 Posted April 16, 2015 I'm not sure but System Idle Power Saver and/or Energy Efficient Ethernet look like they might also want turning off to see if they have an effect 1
6Foot2 Posted April 16, 2015 Author Posted April 16, 2015 Allow only a magic packet to wake the computer need to be ticked. I will give that a go. No newer Intel drivers available.
PeterW Posted April 16, 2015 Posted April 16, 2015 You may need to Disable ErP/EuP in the BIOS if there is such an option. 1
RJohnson91 Posted April 16, 2015 Posted April 16, 2015 (edited) We have these computers also, to get WOL to work we have changed the following in the bios; Under power management: Deep Sleep Control - Disabled Wake on LAN - Set to LAN Block sleep - Block Sleep on S3 state That's what we did to enable WOL, we found by default that all magic packets were allowed through. Also make sure that your computer can't put your network card to sleep when idle. Edited April 16, 2015 by RJohnson91 2
Norphy Posted April 16, 2015 Posted April 16, 2015 We had a problem with PCs with integrated Intel NICs. They all had WOL enabled in the BIOS and in the driver but they still wouldn't wake. In the end, the setting that we needed to enable was one called Enable PME. I can't remember exactly where the setting is set but I still have the registry fragment which we're pushing out with a GPP: Hive HKEY_LOCAL_MACHINE Key path SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0007 Value name EnablePME Value type REG_SZ Value data 1 Setting that and rebooting the machine a couple of times fixed the problem for us. 1
6Foot2 Posted April 18, 2015 Author Posted April 18, 2015 I think we have this now. The answer was to enable WOL but also disable Deep Sleep and Block Sleep [both in Power Management] In other BIOSes we only had to enable WOL to make this work. Also where one setting has an effect on another there is often an explanatory note in the BIOS text pane. Thanks everyone.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now