PdxNet
asked on
Why won't my computer boot up using the Wake on LAN feature anymore?
--Scenario--
I have a couple computers at home that I access remotely from work and other locations using VNC, FTP, etc. I usually leave both of them on but sometimes I like to shut one of them down (and it was shutting itself down for some reason for a while). So I wanted to enable Wake on LAN on one of the computers (called "Galaxo") and wake it up by sending the Magic Packet from another computer (called "Fishy").
I went into the BIOS of Galaxo and set the "Wake on LAN Action" setting to "Power On" (instead of "Remain Off"). I set the ACPI Power State to S3 (the other option is S1). I saved the settings, wrote down the MAC address of Galaxo's on-board NIC, and turned Galaxo off (shut it off completely - not suspend or sleep or hibernate or anything like that). Then I used the command-line utility MC-WOL.exe (http://www.matcode.com/wol.htm), specifying the MAC address of Galaxo's NIC. MC-WOL.exe sent the Magic Packet and Galaxo booted up, just like I expected.
--Problem--
But then a few minutes later, after changing nothing, I shut Galaxo down again and tried the same exact command (MC-WOL.exe) but Galaxo would not turn on. MC-WOL.exe stated that it had sent the Magic Packet successfully, the same as the one time that it worked. I went back into the BIOS to make sure Wake on LAN was still set to Power On and it was. I tried the ACPI Power State "S1" and that didn't fix it. The only other Power Option in the BIOS was Power Failure Action (what to do if there is power failure, which shouldn't effect Wake on LAN).
I also verified that Galaxo's on-board NIC's MAC address hadn't mysteriously changed for some reason (it hadn't). And the ethernet cable was still firmly plugged in to the on-board NIC.
--Specifics--
Galaxo's motherboard: Intel Desktop Board D915GAG/D915PSY (Pentium 4 - 3.8GHz, 1GB RAM)
NIC: Gigabit (10/100/1000 Mbits/sec) LAN subsystem using the Marvel Yukon* 88E8050 PCI Express* Gigabit Ethernet controller
Galaxo and Fishy are on the same local subnet. Galaxo's IP address is 10.0.0.8 and Fishy's is 10.0.0.5.
The only other options that MC-WOL.exe provides are /p [password] and /a [IP address]. /p [password] is only for NICs that support passwords. Mine most likely does not because I've read that few do, and there are no options to change or set a password in the BIOS. /a [IP address] is only if the computers are on different subnets. Mine are not, but I tried the /a switch anyway, to no avail.
And finally, there are no driver or firmware updates for my motherboard or on-board NIC, at least that I'm aware of.
Any help would greatly appreciated!!
~Tony
I have a couple computers at home that I access remotely from work and other locations using VNC, FTP, etc. I usually leave both of them on but sometimes I like to shut one of them down (and it was shutting itself down for some reason for a while). So I wanted to enable Wake on LAN on one of the computers (called "Galaxo") and wake it up by sending the Magic Packet from another computer (called "Fishy").
I went into the BIOS of Galaxo and set the "Wake on LAN Action" setting to "Power On" (instead of "Remain Off"). I set the ACPI Power State to S3 (the other option is S1). I saved the settings, wrote down the MAC address of Galaxo's on-board NIC, and turned Galaxo off (shut it off completely - not suspend or sleep or hibernate or anything like that). Then I used the command-line utility MC-WOL.exe (http://www.matcode.com/wol.htm), specifying the MAC address of Galaxo's NIC. MC-WOL.exe sent the Magic Packet and Galaxo booted up, just like I expected.
--Problem--
But then a few minutes later, after changing nothing, I shut Galaxo down again and tried the same exact command (MC-WOL.exe) but Galaxo would not turn on. MC-WOL.exe stated that it had sent the Magic Packet successfully, the same as the one time that it worked. I went back into the BIOS to make sure Wake on LAN was still set to Power On and it was. I tried the ACPI Power State "S1" and that didn't fix it. The only other Power Option in the BIOS was Power Failure Action (what to do if there is power failure, which shouldn't effect Wake on LAN).
I also verified that Galaxo's on-board NIC's MAC address hadn't mysteriously changed for some reason (it hadn't). And the ethernet cable was still firmly plugged in to the on-board NIC.
--Specifics--
Galaxo's motherboard: Intel Desktop Board D915GAG/D915PSY (Pentium 4 - 3.8GHz, 1GB RAM)
NIC: Gigabit (10/100/1000 Mbits/sec) LAN subsystem using the Marvel Yukon* 88E8050 PCI Express* Gigabit Ethernet controller
Galaxo and Fishy are on the same local subnet. Galaxo's IP address is 10.0.0.8 and Fishy's is 10.0.0.5.
The only other options that MC-WOL.exe provides are /p [password] and /a [IP address]. /p [password] is only for NICs that support passwords. Mine most likely does not because I've read that few do, and there are no options to change or set a password in the BIOS. /a [IP address] is only if the computers are on different subnets. Mine are not, but I tried the /a switch anyway, to no avail.
And finally, there are no driver or firmware updates for my motherboard or on-board NIC, at least that I'm aware of.
Any help would greatly appreciated!!
~Tony
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Cool!