Wakeup on LAN

[KeithDib]

Hi

 

I am trying to get WOL working on a few packages..

 

My packages and SCCM work fine but WOL seems to have a mind of its own..

 

If I hard power off the client machine (hold power button in) my SCCM packages wakes the machine up fine..

If I put client machine in sleep mode through Windows the SCCM packages wake the machine fine

If I Shutdown through WIndows it will not wake up through WOL

 

I only have trouble after Windows has shut the machine down.....

 

I am uing XP pro on clients, SCCM 2007..

 

keith

[anyweb]

well my understanding with WOL is that theres a dirty bit involved, ie: with a dirty shutdown (power off without proper shutdown) the bit is set and WOL won't work until the computer is booted up and shutdown properly

this could be part of your problem, have you looked into that ?

[KeithDib]

well my understanding with WOL is that theres a dirty bit involved, ie: with a dirty shutdown (power off without proper shutdown) the bit is set and WOL won't work until the computer is booted up and shutdown properly

this could be part of your problem, have you looked into that ?

 

 

The dirty bit is responsable for CHKDSK running on start up, I am not sure why this would affect WOL?

 

Tha machines run fine, boot fine and shutdown fine.. its just WOL thats effected

[anyweb]

ok probably bad wording from me then, i'm aware of the dirty bit that's set on a disc if the system is shutdown improperly, and perhaps they are related but from my understanding (and you can test this on real hardware) a 'bit' is set on the nic (network card) to flag if there's been a dirty shutdown or not (at least it was the case on Dell's),

 

try this simple test, power up a computer, shut it down cleaninly, try wol, does it work ? (just send a magic packet)

if it works then power off the same computer by pulling the power while it is in Windows (dirty shutdown) and then try doing a WOL, will it work, most likely not,

 

that's all my point is, and i'm wondering if that is the issue you are seeing

[KeithDib]

ok probably bad wording from me then, i'm aware of the dirty bit that's set on a disc if the system is shutdown improperly, and perhaps they are related but from my understanding (and you can test this on real hardware) a 'bit' is set on the nic (network card) to flag if there's been a dirty shutdown or not (at least it was the case on Dell's),

 

try this simple test, power up a computer, shut it down cleaninly, try wol, does it work ? (just send a magic packet)

if it works then power off the same computer by pulling the power while it is in Windows (dirty shutdown) and then try doing a WOL, will it work, most likely not,

 

that's all my point is, and i'm wondering if that is the issue you are seeing

 

Hi

 

I have tried this...

 

It i shutdown windows correctly WOL does not work... If I pull plug then reinservt plug I can use WOL....

 

Its the opposite to what your would expect

 

Keith

[anyweb]

that's bizzare and exactly as you say it's the opposite of what i'd expect is normal behaviour, but it could be bios version related and/or network driver related

what hardware are you using ? (manufacturer)

[KeithDib]

Its a fujitsu Esprimo E5731, latest BIOS files installed etc

 

The thing is I cant see how it can be BIOS related as it does work when newly plugged in... and as I say is I put machine to sleep it also works, its only after a shutdown. It dont matter if I go to Start/Shutdown or run shutdown from CMD either it still wont WOL...

[anyweb]

try with a different hardware vendor and note the differences, my experiences with WOL are with Dell Hardware only.

 

NIC's asics (the hardware brain of a nic that deals with wol and other things) is frequently updated via a Bios upgrade...

[KeithDib]

We have over 2000 of these machines on the network, trying with another maker is not an option for me

 

Thanks for help though

 

Keith

[anyweb]

are all of your fujitsu's doing the exact same thing ? tried a bios update ? tried a network driver update ?