Wake-on-lan sometimes failed

Hi,
I can make sure that all my settings are correct because
I can wake my PC from remote in most cases.However, it
fails at certain cases:
＊ If I shut-down or suspend my PC for longer time,
say after one night, then it can not be waken.
＊ In the above mentioned case, I have to manually
push the power button and start the PC, after that
if it was shut down, then wake-on-lan function resume
to be in good order
I am wondering if it is because after longer time of shut-down,
the electric current already "fade away" so that the magic
packet can not be properly sent to mainboard.
If my guess is correct, can somebody guide me how to find a
good solution. Thanks.
Here's my system:
Windows XP SP3
Mainboard: MSI G31TM-P21 (MS-7529)
Bios version: AMI V 4.7

Quote from: Bas on 13-October-10, 03:12:24
Check the driver settings for the NIC, and in the BIOS there could be a setting where either BIOS or OS controls it.
If it's set to OS (if you have the option) it must have been shutdown by Windows to make it know the settings.
Ergo after a powercut they are lost.
Bas, sorry I am not so sure what you have instructed me to do.
Here's my power management setup in my Bios, please check
for me and see where is the mistake comes from. Thank you.
(Remark: The option I set was bracketed)
ACPI function: [enable] Disabled
ACPI standby state: [S1] S3
JFP2 power LED function: [Standby LED] Power LED
Power Button Function: [Power Off] Suspend
Restore On AC Power Loss: [Off] On Last State
Wake Up Event By: [Bios] OS
Resume from S3 by USB device [Disabled] Enabled
Resume from S3 by P2/2 Keyboard [Disabled] Enabled
Resume from S3 by P2/2 Mouse [Disabled] Enabled
Resume by PCI Device (PME#) [Enabled] Disabled
Resume by PCI-E Device [Enabled] Disabled
Resume by RTC Alarm [Disabled] Enabled

Similar Messages

SCCM 2012R2 multihomed client, Wake on LAN unreliable

We are seeing a strange problem related to Wake on LAN on client computers with both wired and wireless network interfaces.
All clients are initially imported with the wired MAC address, booted via PXE and image installed. The client then boots up and contacts SCCM. End users then typically use them via wireless and one would expect SCCM to "learn" both the IP/MAC configuration
of the wired and the wireless interfaces. (These networks use separate vlans and IP subnets)
SCCM and our routers are configured for directed broadcasts.
Network sniffing has confirmed that for these clients, SCCM attempts to send the broadcast to the wifi subnets instead of the wired subnets. All directed broadcasts sent to wired subnets have been confirmed to arrive as expected and those clients wake up
as expected.
However, over time the wired network interface appears to be dropped by SCCM, causing Wake on LAN to fail because it obviously won't work using the IP/MAC information for the wireless adapter. When checking the client properties in Configuration Manager,
some clients are incorrectly listed without a wired network interface.
How should we proceed to troubleshoot this issue? Any pointers/ideas/suggestions are welcome.

"one would expect SCCM to "learn" both the IP/MAC configuration of the wired and the wireless interfaces."
Why would one "expect" this?
ConfigMgr uses heartbeat discovery to discover IP address information. What is your heartbeat discovery interval set to?
Jason | http://blog.configmgrftw.com | @jasonsandys

My MPB (late 2013) sometimes fails to "wake up".

My MPB (late 2013) sometimes fails to "wake up". The keyboard light turn on for 1-2 seconds and then turns off again. I have to retry to turin it on several times. Does anyone else have the same issue?

Reset PRAM. http://support.apple.com/kb/ph14222
Reset SMC.     http://support.apple.com/kb/HT3964
    Choose the method for:
    "Resetting SMC on portables with a battery you should not remove on your own".

Wake-On-LAN fails to wake up iMac

I have a 2009 iMac running Mac OS X 10.5.8 and an Actiontec MI424WR Revision E router running firmware version 20.20.8. I am trying to get Wake-On-LAN to work so I can then use LogMeIn whenever I'm away. It used to work several months ago, but now it is not. I have reset the router and tried to redo things since it stopped but I haven't been able to get it to work. I'm not entirely sure of the steps that I need to complete to fix this. Are there any [i]concise[/i] instructions for getting this to work again? Also, I [i]am[/i] aboe to login to my router remotely using Telnet, so is there maybe a way I can generate a "magic packet" with the router so I can skip the deal with port forwarding if the standard method continues not to work?

This tells you how to do it if you have an actiontec router. Also means you don't have to use the risky remote access to router adm maneuver
Note that the doc refers to the default WOL port 9. If you are using a WOL program that uses something other than default you would need to change the settings accordingly
http://www.dslreports.com/faq/verizonfios/3.1_Actiontec#16041

3.2 Server Stuck Offline & Wake on LAN issues

Got through installation and getting started guide running 1 VM Server and a separate VM Manager I was able to shutdown the Server from the Manager GUI; however, when trying to restart the Server from the Manager I received an error: OVMAPI_4005E No worker server found to perform operation on: ovmserv1. I was able to restart the Server by pressing the power button and the Manager was able to recognize the Server as on after it booted. The Manager reports the Server as having Wake-on-LAN 'Yes'. I'm using onboard NIC on Supermicro server, BIOS has a wake on modem feature, nothing for wake on LAN or PCI device. I checked the Server with ethtool and it reported Wake-on-Lan was enabled on both eth0 and eth1. There is an optional IPMI card available for the server but my understanding is that IPMI is only needed if trying to wake from a different network, while everything here is on the same LAN and ping-able. Any help will be greatly appreciated.
Last night I added an Openfiler iSCSI SAN with 3 SCSI targets, one for the pool file , one for the repository and an extra one. Setup server pool, pool file and repository in the Manager. Everything seemed great and I was looking forward to importing some appliances the next day and I shutdown for the night. Today I was trying to setup an FTP server and was messing with LDAP on the Openfiler server, unable to get that going I tried to setup an FTP server on my laptop which is also on the LAN. Later when firing everything up, somehow the NIC on the Manager had been disabled and the Manager was booted without network connectivity. After shutting down the Manager, re-enabling it's NIC and booting up again, the network connectivity was good. The problem is the Manager reports the Server as either Offline when the Server is on, or Stopped(Error) when the Server is off. Using the Manager trying to start the Server fails with 'already on' and trying to stop Server fails with 'not running'. I shutdown and rebooted all 3 servers a couple of times in different orders and the problem persists with the Server still stuck in Offline status. Any help will be greatly appreciated.

Hi,
I uninstalled Mozy a long time ago just because it did prevent my iMac i7 to go to sleep.
I don't know if they have fixed the problem since with an update, or if they'll do it but yes for me back then Mozy = no sleep.
Wake on lan should stay unchecked if you don't need it, this is also known to be a frequent cause of sleep issues.
EDIT : sorry... I didn't read properly your message... My problem was the opposite... Sorry again for my mistake...
Message was edited by: LeDav007

[solved] Cannot activate wake on lan with systemd

I have activated successfully wake on lan with systemd, following these guidelines :
https://wiki.archlinux.org/index.php/Wol#With_systemd
My [email protected] is:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/bin/ethtool -s %i wol g
Type=oneshot
[Install]
WantedBy=multi-user.target
It worked nicely until I recently had to reinstall my server (following a disk replacement). Since then systemd fails to activate wake on lan.
Output from systemctl status wol@enp0s4 :
● [email protected] - Wake-on-LAN for enp0s4
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: inactive (dead) since ven. 2014-07-25 11:21:28 CEST; 23min ago
Process: 181 ExecStart=/usr/bin/ethtool -s %i wol g (code=exited, status=0/SUCCESS)
Main PID: 181 (code=exited, status=0/SUCCESS)
Output from ethtool enp0s4|grep "Wake" :
Supports Wake-on: pg
Wake-on: d
If I explicitly start the service with systemctl start wol@enp0s4, then ethtool enp0s4|grep "Wake" shows:
Supports Wake-on: pg
Wake-on: g
My guess is that the service does not start at the correct timing at boot.
I have also tried wol-systemd package from the AUR without success.
Last edited by elb (2014-07-25 15:02:21)

After a fiew tries and reading docs, I found that replacing network.target with multi-user.target in [email protected] seems to work for me.

Socket wake on lan?

hey guys,
im in the process of writing a client application for a thrid party server, which have no access to.
the application consists mainly of send and recieve online commands, much like a telnet session.
however it can sometime be minutes between communication (totally normal), how do i prevent my socketChannel from droping the connection during these long absences?
also, this socket is in a thread, which simply runs a while(true) loop just checking for any new data on the socket.
is there a way to sleep the thread and awake as soon as data comes in the socket, that its not so exhaustive?
thx guys

sorry for being unclear, im not on a LAN, i was trying to find a feature in java that was similar to the "Wake-On-LAN" featuer built into Network Interface Card, where the thread will put itself to sleep until data comes to the socket, then wake up and do its job. Much like event listeners in GUI's.
Yes, my connection is dropping out. Heres my threaded code
import java.io.BufferedReader;
import java.io.InputStream;
import java.io.InputStreamReader;
import java.nio.channels.SocketChannel;
public class RecvThread extends Thread
     public SocketChannel sc = null;
     public boolean val = true;
     public ServerAuth SA;
     public RecvThread(SocketChannel sc, ServerAuth SA)
          super("Recieve Thread");
          this.sc = sc;
          this.SA = SA;
     public void run() {
          System.out.println("Inside receivemsg");
                    try
               while (val && this.sc.isConnected())
                    InputStream is = this.sc.socket().getInputStream();
                   InputStreamReader isr = new InputStreamReader(is);
                   BufferedReader br = new BufferedReader(isr);
                   String s = "";
                   long pingTime = System.currentTimeMillis();
                   while((s=br.readLine()) != null)
                        if(s.contains("</Data>"))
                             String[] array = s.split("</Data>");
                             for(int i = 0; i < array.length; i ++)
                                  s = (array.contains("<Data>") ? array[i] + "</Data>": array[i] );
                              System.out.println("++ " + s );
                    }else
                         System.out.println("++ " + s);
                    if(!s.equals("QNG"))
                         this.SA.process(s);
                    if(System.currentTimeMillis() > pingTime + 5000)
                         this.SA.process("PNG");
                         pingTime = System.currentTimeMillis();
          catch(Exception e)
               e.printStackTrace();

Wake on Lan will not shutdown

Hello everyone,
I hope I'm posting in the right forum as I think I am simply over looking something.
I have a dual boot system (win 7 and arch) and am trying to get Wake on Lan to work. I have installed ethtool and wol to find my card defaults to receive magic packets (g). I'm using an Asus Rampage IV Extreme mobo with the latest bios. Everything performs as it should with windows when shutting down or hibernating. My issue is when I suspend or shutdown arch it powers down completely and then reboots in a matter of seconds. If I force the card to wol unicast I can suspend the system (sometimes) but will still not shutdown without rebooting. I have used netctl to force the card to wol disabled and I can suspend it everytime. However, even setting wol to disabled, the computer will not shut down. I have disconnected the ethernet cord and even disabled the NIC in the bios but still the same results. If I shut down arch and pull the power when it initially shuts down it simply reboots as soon as power is connected again. The only way I have found to shut it down is to disable "wake on pcie" in the bios. This in turn also disables the windows Wake on Lan. If anybody has an idea of what a solution might be I am all ears (even if it calls for some trolling, I'm sure this deserves some :-)
Thanks in advance

Long standing problem for me and many others.. just google to see this but no solutions, 'linux wol will not shutdown'
https://bbs.archlinux.org/viewtopic.php?id=173648
http://xpenology.com/forum/viewtopic.ph … 82&p=11514
https://communities.intel.com/message/168708
http://serverfault.com/questions/349898 … nt-reboots
http://askubuntu.com/questions/281039/o … ake-on-lan
https://forums.gentoo.org/viewtopic-p-7 … ml#7493630
http://askubuntu.com/questions/132882/w … a-shutdown
http://superuser.com/questions/605324/m … ed-in-bios
Recently, I have been testing several systems (Z77 and H97-based) after I disabled all references to 'xHCI' as it pertains to USB settings. I also enabled wake on keyboard per one suggestion in one of the links above. In about 15 power cycles, I haven't observed an unintentional wake-up with 'wake on PCIe' enabled in the BIOS. More time is needed before I will claim either setting is the fix.
Last edited by graysky (2015-05-03 14:50:27)

Wake on LAN using get-cmdevice ?

Is it possible trigger the WoL feature that is used by SCCM to deploy apps and updates using a Powershell command?
I'm thinking of something like:
get-cmdevice -devicename xyz | do-CMWakeOnLAN
We have WoL functioning but sometimes it is useful to be able to wake up a PC without deploying anything.
Any thoughts?
Neil
PS I know there are 3rd party WoL tools but they don't use the information that SCCM has collected about a device

You may not need to leverage ConfigMgr for this.
http://blogs.technet.com/b/matthts/archive/2012/06/02/wakeup-machines-a-powershell-script-for-wake-on-lan.aspx
Daniel Ratliff | http://www.PotentEngineer.com

GE70 2OE Wake On Lan

Just bought a new GE70 2OE and can't find any power management tab on the bios to try to configure the wake on lan ou usb option. MSI Support won't answer my question. Anybody got a solution?
Thanks

Actually it doesn't require any operating system or higher function, and Apple isn't complying with the wake-on-lan standard by only providing WOL from sleep.
Any PC with WOL can start cold from complete power off. This is all done at the hardware level, no OS at all.
During power off, the power supply is still providing power. Any machine that complies with WOL, keeps the network interface powered up. No IP address, no operating system... just the physical interface watching the raw network traffic.
A broadcast packet containing the NIC's MAC address (unique hardware address, not IP address) should trigger it to tell the machine to power on. In PCs with NICs on the motherboard this is all internal, in PCs with NIC cards, the power is drawn from the constant 5V on the PCI bus, and there is sometimes a small cable connected to the motherboard which is used to trigger the power on (same as the front panel button).
Apple is simply choosing not to implement this feature, it's not because it can't easily be done.
Come on Apple... comply with the standard!

No Wake-On-LAN for powered-down Macs?

I'm relatively new to Mac and don't have a lot of Mac experience or knowledge. Last week I completed the "Mac OS X Deployment v10.4" training in Sydney where the trainer told me that Wake-On-LAN will only work if the Mac in question is in sleep mode -i.e., you can't wake up a Mac that has been shut down. Is this really true?
As an administrator of Windows machines this seems like quite a shortcoming. From where I am sitting I can rebuild any room of computers in any town in my area of control (an area greater than 100,000 square kilometres in NSW, Australia) without having to be there physically to turn on the PCs. At the moment our two Mac rooms are located at my own site, but without Wake-On-LAN, there's no way I could see Macs being deployed anywhere else.
If Wake-On-LAN really does only work with Macs in Sleep mode, then how much power does a 20" Intel iMac draw when in Sleep mode? I really don't like the idea of setting a schedule for every Mac to turn on at a certain time then have them go into sleep mode each and every day on the off chance that I might want to rebuild just one of them. This seems like an awful waste of power to me.
Don't get me wrong, here. I'm not trying to flame because I'm very - very - impressed with Mac in almost every other respect (except the Finder and the Dock) and would switch to Mac long before I stomach Vista, but no Wake-On-LAN to me seems like an incredible stumbling block to Mac adoption.
Intel iMac 20" Mac OS X (10.4.9)

I've already complained of Mac's variation from the "standard" WOL implementation. This problem goes a step deeper as I just discovered.
If in the energy saver options you check the "Restart after a power failure event", the machine will do just that. If the power fails, and then comes back, the machine will boot.
If however, you cleanly shut down the machine, and then power fails, it does not turn back on when the power recovers. All PC's that have auto-power on with AC power restored set in their bios don't care if the machine was cleanly shutdown or crashed... when power comes back, it boots.
The problem here is that when a UPS detects a power failure and eventually decides to shut down the attached computer it should do so cleanly, not by just crashing it (that defeats the purpose of having a UPS!). After the computer turns off, the UPS will turn itself off, cutting power to the computer all together. When the AC power to the UPS returns, and the batteries charge sufficiently, it will turn BACK on, and restore power to the computers.
As it stands now, I have no mechanism by which to force my Mac to boot back up! I could depend on a linux machine on the network (that does behave properly) to send a WOL packet, but it doesn't do that correctly either... so I'm SOL
I can understand having 3 options for reboot after power restore. (1. Restore Always, 2. Restore when system on and power fails, 3. Never Restore).
Only giving us options 2 and 3 is just an oversight of how computers are used in the real world. For the desktop user that may on rare occasion find his machine powered off, and just presses the power button, this is a non issue... But in my opinion this completely eliminates a Mac like this from being used as a webserver/mailserver or other application where uptime is paramount.
I can't believe that Apple would overlook something so important and not provide a mechanism by which a UPS could turn a computer back on after a power recovery. Perhaps there is a non-published setting that doesn't have a check box on a form, that an OEM UPS driver would set that says "pretend you crashed".

Wake on lan from power OFF

It appears that Mac's don't provide wake on lan from complete power off. I have no problem powering up my Mac from sleep, but it won't turn on from power off (like every PC I've tried). This is not difficult to do, as every $200 PC on the market w/ WOL does it.
I have my Mac on a large shared UPS with serveral other computers and network gear, etc.
There is a linux server which actually communicates with the UPS. During a power failure, that linux box will connect to ever other machine on the network sharing this UPS and tell them to SHUT OFF, not sleep, because hard power failure is emminent. When all remote machines are off, the linux machine shuts off, and the UPS powers off it's outlets.
On power recovery, the UPS waits until it's batteries are sufficiently recharged, and turns back on, powering up it's protected outlets. All the machines see power come back on, and are set to reboot.
Here is the problem. If the power comes back on AFTER the remote machines are shut down, but before the linux box turns off, the linux box sees power recovery, and the UPS never shuts off it's protected outlets. Now all the remote machines are off, and won't ever see their power cut off, and then recover, so they don't turn back on.
The PCs are easy... hit them with a wake-on-lan packet and they reboot from complete power off... but not the trusty Mac because Apple didn't implement that part of the wake-on-lan standard!
So... I'm faced with abandoning wake on lan for all the machines and building an interface with a big relay to KILL power to all remote machines to power them back on. Isn't this more than just a little silly? Apple... why not just make your machine comply with the standard so that it plays nicely in a mixed environment!
Providing wake on lan from sleep, and power on with power recovery, but no wake on lan from OFF is just ridiculous.
I welcome any ideas...
PowerMac G5 Dual 2.0 Mac OS X (10.4.8)

Malcolm,
If I make it sleep, then I'm forcing it to crash when the power turns off. The idea here is for a graceful shutdown before emminent power failure when the UPS battery runs out.
The only reason it's getting shut down is that the main power has failed and the UPS battery is running low.
I agree that with no power they can't interpret packets and react... but that's why proper wake-on-lan implementations keep the NIC powered up to watch for WOL packets.
Thanks,
-Russ

SCCM 2012- Wake on LAN

Has anyone tested Wake On LAN with SCCM 2012? I am getting error 0x80072741 in wolcmgr.log. Any help is much appreciated.
Divya

Hi, here is the snipped from the wolcmgr.log. Also another update, now during our testing we can see that if the machine is in Sleep mode, they wake up at the time specified. However they don't wake up when they are in Hibernate mode.
Even though the machines are waking up, but we still get the same errors in WOLCMGR.LOG. Not sure if we can ignore them or if they are something to worry about.
Any help will be highly appreciated!
WOLCManager one or more existing jobs is ready.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3412 (0x0D54)
WOLCManager executing job id='4715d87' in state 'STATE_PROCESSDATA'.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3412 (0x0D54)
WOLCManager processing data for job id='4715d87'.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3412 (0x0D54)
Preparing to send a wakeup packet to client with IPAddress=xx.xx.xx.xx, IPSubnet= and MACAddress=xxx.xxx.xxx.xxx
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
WOLCManager failed to send the wakeup packet (0x80072741)
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
Preparing to send a wakeup packet to client with IPAddress=xx.xx.xx.xx, IPSubnet=xxx.xxx.xxx.xxx and MACAddress=xx:xx:xx:xx:xx:xx
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
WOLCManager waiting 5 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER
8/23/2012 5:47:01 PM 3412 (0x0D54)
Preparing to send a wakeup packet to client with IPAddress=xx.xx.xx.xx, IPSubnet=xxx.xxx.xxx.xxx and MACAddress=xx:xx:xx:xx:xx:xx
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
STATMSG: ID=6507 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_COMMUNICATION_MANAGER" SYS=server.domain.com SITE=PRI PID=1204 TID=3428 GMTDATE=Thu Aug 23 12:17:01.464 2012 ISTR0="CAS20007" ISTR1="1" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=3 AID0=422 AVAL0="4715d87" AID1=421 AVAL1="1" AID2=415 AVAL2="CAS20007"
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
WOLCManager encountered an error while sending packets (0x80072741)
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
WOLCManager retry for job id='4715d87' - 2 retries of 3 maximum completed).
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:01 PM
3428 (0x0D64)
Persisting job data for job id='4715d87'. SMS_WAKEONLAN_COMMUNICATION_MANAGER
8/23/2012 5:47:01 PM 3428 (0x0D64)
WOLCManager one or more existing jobs is ready.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:06 PM
3412 (0x0D54)
WOLCManager executing job id='4715d87' in state 'STATE_PROCESSDATA'.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:06 PM
3412 (0x0D54)
WOLCManager processing data for job id='4715d87'.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:06 PM
3412 (0x0D54)
WOLCManager job id='4715d87' will execute next in at least 56 seconds.
SMS_WAKEONLAN_COMMUNICATION_MANAGER 8/23/2012 5:47:06 PM
3412 (0x0D54)
WOLCManager waiting 56 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER
8/23/2012 5:47:06 PM 3412 (0x0D54)
Divya

975x Platinum PowerUp - Wake on LAN problem...

Hi,
for TV digital cable recording with my DboxII receiver (Neutrino Linux) I need Wake-on-Lan. It work flawlessly with my old ASUS A7N266-C: PC as streaming server, woken up by the pre-programmed DBox by a "Magic Packet" containing the MAC-adress of the LAN-card. (So I don't have to program any timers on the PC, just have to be sure that it is in standby or hibernation mode.)
The new setup is the same as the old, I've only changed the PC's MAC-Adress in the DBox-setup. The DBox is connected via router.
What I've done: I activated PME in the Intel LAN properties, and activated "resume by directed packets and Magic Packet". I allowed the device to wake up WindowsXP and set the BIOS to resume by PCI and PCI-E events (seems as if PCI-E is the necessary setting for the onboard LAN).
What happens, is, that it doesn't work with Magic Packets. It almost works with this "directed packets" setting - but the problem is, that the PC only stays in hibernation mode for around 15 seconds - even if the Dbox is switched off. Maybe the router does something to wake the LAN card? DHCP is already off...
Has anyone further knowledge about WOL with this board? The next thing I'll try is, if it works better with my previous Realtek PCI card. But it would be a pity to waste a PCI slot for that....
Power-on-LAN is impossible with this board, I guess?
Martin
P.S. I'm still stuck to BIOS 7.1, because I need the Intel Raid AND the JMicron IDE - is there any beta BIOS, that I could try?

Quote from: FrobinRobin on 27-November-06, 23:25:47
I've had WOL work on various BIOSes. I know 100% it works with 7.1A.
You need to select the first boot device as LAN
I tested my WOL application firstly from the shell prompt from another PC and when it worked I set up a web page to run the WOL app - it works great but if i remember correctly I had to change some firewall settings(?) to get it working from the shell. If you cannot get it to work maybe there is a compatibilty issue with the mobo & dbox WOL packet ?
(i have dbox - they're gr8 )
I use WOL 1.1 by Greg Whittmeyer (PM me if you want a copy)
Every magic packet is the same - the mac addy 3 times, so it shouldn't matter how it's being generated. If you want to test your waking app, plug another computer into the same network cable as the 975 system and send it's magic packet.
Another thing to be sure of is to make sure your power is off, magic packets will sometimes not wake a sleeping computer - from S1, S3, or S9

Wake on lan only from sleep?

Is Wake On Lan (Wake for Ethernet network administrator access) only available when sleeping, and not when powered down?

Actually it doesn't require any operating system or higher function, and Apple isn't complying with the wake-on-lan standard by only providing WOL from sleep.
Any PC with WOL can start cold from complete power off. This is all done at the hardware level, no OS at all.
During power off, the power supply is still providing power. Any machine that complies with WOL, keeps the network interface powered up. No IP address, no operating system... just the physical interface watching the raw network traffic.
A broadcast packet containing the NIC's MAC address (unique hardware address, not IP address) should trigger it to tell the machine to power on. In PCs with NICs on the motherboard this is all internal, in PCs with NIC cards, the power is drawn from the constant 5V on the PCI bus, and there is sometimes a small cable connected to the motherboard which is used to trigger the power on (same as the front panel button).
Apple is simply choosing not to implement this feature, it's not because it can't easily be done.
Come on Apple... comply with the standard!

Wake-on-lan sometimes failed

Similar Messages

Maybe you are looking for