Reply to thread

Message

<blockquote data-quote="blackheart42" data-source="post: 250138" data-attributes="member: 25694">I'm setting up a file server to do the same thing - wake up on access and go to sleep later.&nbsp; I'm having problems with other things, but the wake/sleep part works well.Depending on your server's NIC card, you may not need magic packet at all.&nbsp; Check the card's options for something like 'wake on directed packet' or 'wake on unicast'.Next, I found that on my client system I needed to do two things to get this to work.&nbsp; First, add an entry in the host file for the server.&nbsp; This also implies that your server uses static addressing.&nbsp; Second, run a batch file in your startup folder that has this command:&nbsp; arp -s &lt;IP address of your server&gt; &lt;MAC address of your server's NIC card&gt;.&nbsp; After this, clicking on the server's shared directory in Windows Explorer causes the server to wake up.&nbsp; Depending on the server, the client may timeout and say that the server isn't available.&nbsp; Wait a few seconds and try again.Apparently some NIC cards support wake on ARP.&nbsp; If you've got one of these, the client changes probably aren't necessary.I don't know of a way to send the magic packet every x minutes.&nbsp; I just set the sleep timeout long enough that it doesn't matter - maybe 10-15 minutes.&nbsp; If I want to access the server beyond that it just goes to sleep and I wake it up again.&nbsp; Of course, that timer doesn't apply while I'm accessing the drive - i.e. watching a movie or copying a file.&nbsp; It only starts after I stop accessing the server.Blackheart</blockquote>

[QUOTE="blackheart42, post: 250138, member: 25694"] I'm setting up a file server to do the same thing - wake up on access and go to sleep later. I'm having problems with other things, but the wake/sleep part works well. Depending on your server's NIC card, you may not need magic packet at all. Check the card's options for something like 'wake on directed packet' or 'wake on unicast'. Next, I found that on my client system I needed to do two things to get this to work. First, add an entry in the host file for the server. This also implies that your server uses static addressing. Second, run a batch file in your startup folder that has this command: arp -s <IP address of your server> <MAC address of your server's NIC card>. After this, clicking on the server's shared directory in Windows Explorer causes the server to wake up. Depending on the server, the client may timeout and say that the server isn't available. Wait a few seconds and try again. Apparently some NIC cards support wake on ARP. If you've got one of these, the client changes probably aren't necessary. I don't know of a way to send the magic packet every x minutes. I just set the sleep timeout long enough that it doesn't matter - maybe 10-15 minutes. If I want to access the server beyond that it just goes to sleep and I wake it up again. Of course, that timer doesn't apply while I'm accessing the drive - i.e. watching a movie or copying a file. It only starts after I stop accessing the server. Blackheart [/QUOTE]

Verification