nsainfreek

Wake Server When Accessing Network Shares

11 posts in this topic

I posted this on a different forum but was told to try and present the question here as the people here may be more knowledgable. I don't run WHS but was hoping you guys could still help me. I'm running Windows 7 Ultimate with a DIR-665 Router and have also tried a Netgear WNDR3700 Router.

I have a server with all my movie files and I would like to share them with other computers on my network. The other computers would mount network shares on their computer in order to access the server. However, the server is not accessed most of the times since it is a home server and I would like it to go to sleep when not in use. I could enable Wake-On-Lan, but that is an extra step to send a magic packet to wake the server up. I would like the server to wake when someone attempts to access one of the network shares.

There is the option of waking on ping, which would wake the server whenever there is any attempted communication. This is probably the path I want to take. However, with this option on the server wakes after just two minutes of going to sleep and does not go back to sleep. After reading a lot of threads on the web, it seems the router is doing an arp refresh (not sure if that's the right terminology). The router is asking "who has this ip address" and it hits all the computers on the network, which wakes the server. The router does this like every 2 minutes. Some people online have said that they got wake on ping to work properly but those were old threads and I couldn't get any answers.

Anyway, I've tried assigning static IPs on the network, shutdown the dhcp server, and bought a new router. Computer is still waking up shortly after going to sleep. I read somewhere that you can edit the arp table so that it doesn't bother the computer, but I'm not sure if that's possible since I have found no documentation of editing arp tables on routers.

Does anyone know if and how this can be done? Any response would be useful thanks.

Share this post


Link to post
Share on other sites

Upgrade to a WGS Supporter Account to remove this ad.

You'd need to connect to the router through telnet and create a static ARP entry for the WHS IP using arp -s. Whether or not that will survive a reboot is doubtful though.

Never heard of Wake-On-Ping - learn something everyday :)

Share this post


Link to post
Share on other sites

You'd need to connect to the router through telnet and create a static ARP entry for the WHS IP using arp -s. Whether or not that will survive a reboot is doubtful though.

Never heard of Wake-On-Ping - learn something everyday :)

So you're saying that if I create a static ARP entry the router would probably fail to boot? That's probably not what I want to do then. Any other ideas? I thought that other people may be trying to accomplish such a setup to have a mix of 24/7 accessibility, ease of use, and power savings. Apple has it's Wake-on-demand functionality which works by having the router send the magic packet while using bonjour to broadcast the services of the server. This would work except Mac's aren't really expandable (beside the Mac Pro) and I have around 10 HDs running in my server.

Is it possible to do something where if you try to access a network drive it auto sends a magic packet?

Share this post


Link to post
Share on other sites

The apple thing sounds most cool. What I mean is that the static arp cache entry won't survive a router reboot, i.e. it will go back to being dynamic when you reboot the router for any reason.

Wake-On-Lan is just a packet with the MAC address repeated six times; I think the best you'll end up with is a scheduled task to send a wakeup packet periodically when the machine is on (or at logon) using the Windows task scheduler. I'm increasingly finding uses for a super-low-power box running from flash, and this is one example. It could sit there on the LAN, and send a WoL packet when it spots an arp request to the specified IP address (arp is the very first packet that will be sent when you try to make the connection and, since it's a broadcast, can easily be detected). I a netbook might fit the bill, but the packback period would be quite long.

Share this post


Link to post
Share on other sites

Thinking about this some more an agent could easily be devised to run on the PC itself, bypassing the need for the centralised monitoing box. But not be me unfortunately :(

Share this post


Link to post
Share on other sites

The apple thing sounds most cool. What I mean is that the static arp cache entry won't survive a router reboot, i.e. it will go back to being dynamic when you reboot the router for any reason.

Wake-On-Lan is just a packet with the MAC address repeated six times; I think the best you'll end up with is a scheduled task to send a wakeup packet periodically when the machine is on (or at logon) using the Windows task scheduler. I'm increasingly finding uses for a super-low-power box running from flash, and this is one example. It could sit there on the LAN, and send a WoL packet when it spots an arp request to the specified IP address (arp is the very first packet that will be sent when you try to make the connection and, since it's a broadcast, can easily be detected). I a netbook might fit the bill, but the packback period would be quite long.

So If I input a static arp entry into the router, it'll be ok as long as I don't reboot the router? And I could just reinput the arp entry if the router was to ever need rebooting, correct? Do you know where I could look for instructions to access a router via telnet?

Scheduled task wouldn't work well for me since the system is not used at regular time intervals. What would need to be created to send a WOL when an arp request to a specified IP is sent out? Would it be a process or program? I'm not sure what you mean when you say "running from flash." Are you talking about a flash program?

Thanks for your responses so far!

Share this post


Link to post
Share on other sites

Yes the router would be fine. Scheduled tasks can be set to run at logon and periodically (say every 5 mins).

Running from flash, as in a USB flash drive instead of a hard disk for an uber-low-power PC.

Re my agent idea, yes a compiled program that monitors the LAN (like Network Monitor does) and, when it sees the packet, sends a WoL packet. Maybe something like ArpAlert could be adapted, I might have a ponder on this over the weekend as it would be highly useful for me...

Cheers!

Share this post


Link to post
Share on other sites

Yes the router would be fine. Scheduled tasks can be set to run at logon and periodically (say every 5 mins).

Running from flash, as in a USB flash drive instead of a hard disk for an uber-low-power PC.

Re my agent idea, yes a compiled program that monitors the LAN (like Network Monitor does) and, when it sees the packet, sends a WoL packet. Maybe something like ArpAlert could be adapted, I might have a ponder on this over the weekend as it would be highly useful for me...

Cheers!

Alright, i'm going to try and see if I can figure out how to telnet into my router and make an arp entry. If you figure anything out, please let me know. Thanks!

Share this post


Link to post
Share on other sites

Well, I can't figure out how to input a static arp into the router. First off, I can't figure out how to telnet into the Dlink Dir 665. I managed to telnet into the Netgear wndr3700 but it won't let me create a static arp. When i use the "arp -s" command it doesn't seem to do anything. Any other recommendations would be appreciated.

Share this post


Link to post
Share on other sites

Hi nsainfreek

I know this is an old thread but did you ever get anywhere with your wake on demand.

I've just installed WHS 2011 and would love the server to be able to make when a request is made by my Sonos or Apple TV2.

Does anyone out there know how to make this work?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now



Upgrade to a WGS Supporter Account to remove this ad.



  • Posts

    • I get the above error dialogue when I run the connector on my Win 10 pro client.  Followed the issue resolution on TechNet which say start cert service in IIS on server but this was already running.   I've downloaded the Win 10 connector with no joy also.   Please help.
    • Dave, can you clarify what you mean by this?
    • I had no problem with Windows 10.  However, I just completed the anniversary update and now the "Connector" won't run to conclusion.  It backs itself out and reports an unspecified error.
    • Apologies if I'm being stupid, but I'm having great trouble understanding how Lightsout backup and the Server Essentials 2012 backup work together (or fight with each other). I find the Lightsout documentation on this very unclear, and various threads have left me no wiser. I'd appreciate some help! Here's the setup: Lightsout is running nicely on the server. Before backups were set up, I established that the server hibernated when the clients were switched off. The server woke up when a client was powered up. (This behaviour broke when backups were set up.) The server is Essentials 2012, with a number of client laptops: a mix of Windows 7, 8 & 10. The Essentials backup window is 22:00 - 07:00. No backup settings are currently made in Lightsout. Here's what I'd like to achieve: At the end of the working day all the clients are put to sleep or hibernate (or switched off completely, I don't care which). Ten minutes after that, Lightsout hibernates the server. Sometime during the night (22:00 - 07:00) the server wakes up, then wakes up the various clients in turn, backs them up, and puts them back to sleep / hibernate / shutdown (I don't care which). Here's what actually happens (when I look at the uptime chart the next morning): At the end of the day (about 17:15) the clients are put to sleep / hibernate. (I tell the team not to shut down their client laptops because I assume the server can't wake a completely shut down client - is that correct?) The server does not hibernate. Approximately 90 minutes after the clients were put to sleep / hibernate, they all wake up simultaneously (around 18:45, but I don't know why this happens). The clients then stay awake all night. Later, from 22:00, some of the backups take place (but not all of them). The backups are spread wide apart in the 22:00 - 07:00 window with lots of time when nothing is going on at all. The clients do not go back to sleep / hibernate after their backups. ...can anyone suggest what combination of settings I should be using to get the desired behaviour? Here are the sort of things that are confusing me, but I can't find definitive answers (and each experiment I do takes 24 hours to give any results!): I know I can specify clients' individual backup times in Lightsout, but I don't know how long a client's backup will take, so I could have backups overlapping each other and causing a traffic jam. Should I worry about this? If I set Lightsout backups, what do I set for the Essentails backup window? What if it's not long enough to get all the backups done? If I make settings in the Lightsout backup dialog do I have to complete everything in that dialog box? Does this make the Essentials 2012 backup settings redundant? What about the Essentials 22:00 - 07:00 backup window, does that matter any more? I tried setting client backup times in Lightsout with an end action of 'sleep'. The backups didn't happen at all and clients all spontaneously went to sleep in the middle of the working day (the server / clients clocks all match, I checked). Can Lightsout wake up a client laptop that is completely shut down? Thanks for reading this long post and sorry if these seem like stupid questions. I already have WHS2011 / Lightsout running perfectly on another setup (where my backups take place during the day), but nocturnal backups are a new level of complexity for me!
    • Christopher wrote:  << And to clarify, if you want multiple backup drives to be cycled offsite, you MUST connect all of them at the same time when you set up the backups. >> I'm not clear about this. To the best of my recollection, I never connected both of my backup drives to the server at the same time,  For test purposes, I just initiated a recovery (using the WHS Installation Disk) with each of them hooked up.  The one that has been offsite and the one that backed up last night were both found by the "Repair an existing installation" procedure.  Perhaps I'm misreading your clarification.
  • Popular Contributors