Mboard with no Wake-On-LAN, please help!

[tomfinnie]

I'm in a very similar position as you farquea, with 100 new H61M-P23 boards installed. I've spent over an hour trying to fix this, trying every possible permutation of relevant settings without success, updating the BIOS, changing power settings to OS controlled rather than BIOS, and setting the OS settings to wol on magic packets and wake from shutdown, disabled EUP2013. Nothing's worked. It won't even WOL from S3. It won't even USB device wake from S3. The whole power control thing seems to be FUBAR in fact. Avoid this entire range of MSI boards if WOL is important to you.

[farquea]

I'm in a very similar position as you farquea, with 100 new H61M-P23 boards installed. I've spent over an hour trying to fix this, trying every possible permutation of relevant settings without success, updating the BIOS, changing power settings to OS controlled rather than BIOS, and setting the OS settings to wol on magic packets and wake from shutdown, disabled EUP2013. Nothing's worked. It won't even WOL from S3. It won't even USB device wake from S3. The whole power control thing seems to be FUBAR in fact. Avoid this entire range of MSI boards if WOL is important to you.

 

I found that you can set the bios wake to anything and they wont actually affect waking from keyboard and mice in windows. if you "Standby" the pc in windows you can wake it from cliknig the mouse or pushing a key on the keyboard but you have to go into device manager and go into the properties of your mouse and keyboard and tick the box that says "allow this device to wake the computer" do that and it works for me fine, like i say regardless of what is set in the bios, agreeing that it just doesnt seem to work at all the bios wake features.

 

This way i'll have all of them go to standby after 2 hours idle and hopefully overnight it wont be getting TOO hot in the cupboards or use too much elecricity. I have just found one downside though. for the updates to be installed that WSUS dishes out, you have to do "shutdown and install" if i'm not going to be shutting the PCs down, only logging off then no windows updates will get installed until i go round and shut them down myself and then have to switch them all back on one by one!

[PeterW]

Well WOL should certainly work on these boards I guess there must be a pretty big BIOS bug at the moment, I will give MSI a nudge and see if they have any ideas.

[tomfinnie]

You can set WSUS to schedule an install and restart at a given time. In group policy, Computer>Policies>Admin templates>Windows Components>Windows updates>configure automatic updates and then set;

 

Configure automatic updating: 4 - Auto download and schedule the install

Scheduled install day: 0 - Every day

Scheduled install time: 16:00

 

or somesuch.

 

Or just script a restart every so often with shutdown -r -t 0 -m \\machine. Or psshutdown if you want to feed it a list of machines or give users a cancel option.

[PeterW]

Could you try and set the "WOL & Shutdown Link Speed" option in the driver to 100Mbps first. I think by default it will be set to 10Mbps first.

[farquea]

Could you try and set the "WOL & Shutdown Link Speed" option in the driver to 100Mbps first. I think by default it will be set to 10Mbps first.

 

tried, doesnt appear to have made any difference

[farquea]

Ook got it working!!!! Now waking up from full shutdown... even though the NIC LED's are all off. Heres what i did (although really its a combo of what i was told yesterday, i just was accepting that no LEDs meant it wasnt going to work and didnt really try any WOL programs enough)

 

In BIOS it needs;

 

1.Enter bios to set “LAN option ROM” enable.(Integrated Peripherals-> LAN option ROM)

2.Enter bios to set “Resume By PCI or PCI-E Device”enable.(Power management setup->Wake up Event Setup)

3.EUP 2013 DISABLED!!! (this was the key, if this is enabled it wont work for me)

 

and that is it, ive even unticked "allow this device to wake the PC" in the network adapter properties in windows and its working.

[PeterW]

Glad to hear it is working now

 

Hopefully with your feedback @tomfinnie can get his working as well.

[tomfinnie]

Unfortunately the exact configuration listed above hasn't worked for me.

[farquea]

Unfortunately the exact configuration listed above hasn't worked for me.

 

what program are you using to WOL?

[tomfinnie]

Tried it with wolcmd and out antiquated disc imaging / system management package. Neither worked and they're working fine with other machines plugged into the same patch etc.

[farquea]

wol.exe i find a good test, once i knew it was working with this, tried again with NetSupport and worked fine. The computersa you are sending the packets from are on the same subnet as the clients i assume?

[smitesh]

Hay guys to let you know I got it work with above "FARQUEA" suggested settings thank you