Wake on lan

[mrbios]

Asking this in here because it's more the sort of thing you lot would deal with then the people in the motherboards section....

Wake on lan runs on every PC on our network, except this one particular type of motherboard:
Foxconn 946GZ7MA-8KRS2H - Latest bios
Marvell Yukon 88E8001/8003/8010 PCI Gigabit controller - Onboard

The issue i notice is that no power is going to the network socket when the board is powered off, every other board around the network still has a connection light on once the PC has powered down.

The setting for wake on lan in the bios is enabled
The windows setting for wake up from lan is enabled

I can PXE boot ok, when PXE is enabled, if PXE is enabled the network lights on the board come on when it begins attempting to connect.
If PXE boot is disabled then the network lights come on the instant windows begins to load.

Does anyone have ANY idea because it's driving me mad >_<

 

[mrbios]

S5, There is an option in the bios for it (which is enabled) other boards with the same intel 946 chipset work with it (though those have realtek onboard network controllers opposed to marvell yukon)

The board clearly states it supports wake on lan on the foxconn website, but for the life of me i can't get it to work even though it works everywhere else, i've also checked that theres nothing funny going on with any of the switches as well by putting another board in the same building and that boots fine.

It's a head scratching problem

 

[mrbios]

Well one thing i noticed earlier, was that i turned on PXE boot, went into a PXE window (in this case a network bootable version of windows PE) then shut down the PC by the power button and the network lights stayed on, but attempting a WOL during this state it reported that "no host available" or something to that effect, turning it on and loading it into windows again folloed by another shutdown the lights went off

It's very strange behaviour, so strange that im starting to think that the boards are actually at a design fault!

I will give hibernation a go though and see what i get

 

[mrbios]

I think im going to specificly avoid marvell yukon network controllers from now on, although realteks drivers are flakey at times they always seem to just work with WOL, might look into getting 75 really cheapo network cards to put in these machines or something, that'd fix it im guessing (buy one to test first)

Trying to be a bit more eco friendly (for some reason...i feel dirty saying that)

 

[mrbios]

Looking back the last lot were Marvel Yukon and I had the same problem with those!

Are you turning on a lot of machines? 10s?100s?

around 400-450 machines i have set up for scheduled shutdown every night at 10pm (have to allow for parents evenings, its a school network) and then they switch on at 7:30am on scheduled WOL

Handy little AD integrated program called spec ops remote admin

there are 55 machines in total which don't work, all are the same board all purchased at the same time

 

[mrbios]

Look at it this way, even if the 55 weren't shut down you are still making a saving.

By shutting down at 10pm when do you plan for them to do windows updates, disk defrags etc? Are you boarding too?

Windows updates install at 4pm, there is very very little going on between 4 and 10 so those tasks run then

 

[mrbios]

sigh...ive fixed it and i can't believe it was so simple

Network adapters > properties > configure > advanced > "wake from shutdown" to on
Then the power management tab and set "allow this device to bring the computer out of standby" which i had actually already done!

Gah kicking myself, i ever looked though that list i must have just glanced over the damn thing >_<

 

[mrbios]

intel recommends that wake on lan is disabled to save power.
that would be the best option in the home
just thought id chime in

This isn't for home, it's actually used in order to save power at work

about 350PCs are set via a schedule to shutdown at 10pm then WOL at 7am, as a lot of our PCs aren't in cases, there fitted to boards which are in closed locations where only we (the IT folk) can turn them on