- Wake on Lan power on from S5 state: I'm stumped
- Posted by Karl Breiner on October 29th, 2005
I have an older motherboard (440bx agp set) with a BIOS that supports
wake on lan via a 3-pin header. When I set the BIOS to enable WOL, I
can successfully send a magic packet and turn on the computer from an
S5 (power off) state.
HOWEVER, the minute I run Windows Server 2003 and do a system
shutdown, the WOL no longer works!
Based on these observations, the OS would seem to be interfering with
WOL operability in some way. I'm using an Intel Pro 100 card, and
have read through the documentation, playing with the advanced
settings of the card, to no avail.
My hope is that there is some brilliant Windows registry hack that
will make this work. Anyone have any ideas?
Thanx,
Karl
- Posted by kony on October 29th, 2005
On Sat, 29 Oct 2005 16:36:44 -0400, Karl Breiner
<KarlB26@yahoo.com> wrote:
Have you looked for a setting in the NIC properties (in
network connections)?
Loading a driver can toggle the functionality of the NIC,
and may do that depending on the default driver setting.
Have you tried another NIC driver (if there is no such
setting in the NIC properties)?
- Posted by Karl Breiner on October 30th, 2005
On Sat, 29 Oct 2005 20:48:17 GMT, kony <spam@spam.com> wrote:
I've messed with the properties of the NIC quite a lot. I've adjusted
the obvious settings.
For "Wake On Lan Settings", there are these choices: Disabled, OS
Controlled, Wake on Magic Packet, Wake on Directed Packet, Wake on
Magic and Directed. I have it set on "Wake on Magic Packet" right
now, but I've tried them all.
"Wake on Link Settings" choices are Disabled, Forced, and OS
Controlled. I have it set to Forced, but I've tried them all.
"Enable PME" I have set to Enabled.
These would seem to be the obvious settings to mess around with, and I
think I've tried them all. Unless there is a config file or ini file
somwhere to mess with?? I dunno.... but thanx for the help.
