• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WoL works only with magic packet

MikalCarbine257

Senior member
Hi all,

I have a desktop running Windows 10 Pro with an MSI Z77MA-G45 and just set up a 4TB Raid 1 array as a network share for my local PCs in my house to share. I want my desktop to wake when another device tries to access the shared disk. I've done some reading and I've managed to successfully set up wake on lan with the magic packet and test it using Depicus' wake on lan GUI. My problem is when I disable the magic packet the wake on lan seems to stop working. I tried arping and pinging my desktop to wake it but it doesn't wake it up. I'd like to be able to get this to work without the magic packet.

I've done some reading that the Realtek PCIe driver might play a role with this. I updated it to the latest version on the Realtek website but a lot of people recommend rolling back to an old driver? Something about the onboard NIC shouldn't have the PCIe driver however on the MSI Z77MA-G45 driver page it is listed as the PCIe driver. Any suggestions?
 
Srsly. What would be the point? Just leave your "server" PC on all the time. Maybe set the monitor and HDDs to power off and spin down, respectively, after a certain time period passes (10 min).

The reason that I say this is: "Windows File-sharing" networks are chatty. Lots of broadcast frames, which, in your case, would be waking up the PC left and right. So, there wouldn't be a point to non-magic-packet WoL.
 
Really just power consumption, I have no idea what my desktop draws but I'd imagine its in the 50W+ range at idle. No point in leaving it on and wasting money and energy when it won't be used for 14+ hours during the day when a couple of software settings could enable the same functionality
 
Really just power consumption, I have no idea what my desktop draws but I'd imagine its in the 50W+ range at idle. No point in leaving it on and wasting money and energy when it won't be used for 14+ hours during the day when a couple of software settings could enable the same functionality
1) Buy a standalone NAS box
2) I don't think that you understand how this all works.

I admit, it would be nice if there were some way for the higher-level Windows File Sharing, to send a Magic Packet over the ethernet to wake up a server, before attempting to access a share. I don't know if this is possible or not, I've never had to occasion to try to configure that.

But, ethernet networks have "broadcast frames", as well as "directed frames", which are sent quite often by Peer nodes on a Windows File-Sharing Network.

If you didn't use Magic Packet, and these constant broadcast frames would wake up a PC, then it would be pointless to power it off or put it to sleep.

Ethernet works at a lower level, than Windows File Sharing protocol. It is not as simple as just configuring "wake this PC, when I access this Server/Share combination", like you seem to think it is.
 
Last edited:
Back
Top