locked
Ok this is stupid? By design? RRS feed

  • Question

  • I would like to remotely connect from work to my home computer through WHS but would also like to make my home computer sleep.

    When I visit my WHS home page (remote access), my computer is listed and ready to be remotely connected to however, it’s listed as offline or sleeping…well it’s not offline, but is indeed sleeping, why is there no option to wake it up? That’s stupid; obviously I want to use it and should wake up?

    What kind of design process this went through. Unless it’s some kind of security thing, but I don’t understand as I need to provide credentials to log in to WHS homepage and then again to remotely connect to my home computer.

    Can someone shed some light on this?

    Tuesday, August 11, 2009 4:05 PM

Answers

  • try installing the WOL addin... it cost's about $20... well worth it...

    https://angelo.homeserver.com/ehtech/store/product/80de89b7-59b6-4d59-bdfc-2176abec1d0f.aspx

    It works great for me...

    I also installed the remote alert addin... That one was free...
    you can find a list of addins on the following page
    http://whsaddins.com/

    Cheers
    Bryan Clark
    Vancouver, Canada
    • Proposed as answer by B Clark Tuesday, August 11, 2009 4:19 PM
    • Marked as answer by Ken WarrenModerator Friday, February 12, 2010 6:47 PM
    Tuesday, August 11, 2009 4:19 PM
  • Wake On LAN isn't built into Windows Home Server because it requires support and specific configuration in a client computer's BIOS and operating system. Not every computer supports WOL at all, and the configuration is not normally done either by the computer manufacturer or the purchaser. It would be possible, I suppose, for the installation of the connector to configure the operating system correctly, but it's not really possible for the connector to change the BIOS configuration.

    Even if a computer is configured to support Wake On LAN, not every motherboard/BIOS does so in a useful fashion. There is hardware available which, if configured for WOL, will wake up to any network traffic. That sounds desirable, but in reality, such computers will generally be awakened by other random traffic on your LAN within a few minutes of being put into a power saving state.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, August 11, 2009 8:31 PM
    Moderator

All replies

  • try installing the WOL addin... it cost's about $20... well worth it...

    https://angelo.homeserver.com/ehtech/store/product/80de89b7-59b6-4d59-bdfc-2176abec1d0f.aspx

    It works great for me...

    I also installed the remote alert addin... That one was free...
    you can find a list of addins on the following page
    http://whsaddins.com/

    Cheers
    Bryan Clark
    Vancouver, Canada
    • Proposed as answer by B Clark Tuesday, August 11, 2009 4:19 PM
    • Marked as answer by Ken WarrenModerator Friday, February 12, 2010 6:47 PM
    Tuesday, August 11, 2009 4:19 PM
  • Thanks!

    Wonder why this isn't built in already, seems retarted?
    Tuesday, August 11, 2009 4:31 PM
  • Wake On LAN isn't built into Windows Home Server because it requires support and specific configuration in a client computer's BIOS and operating system. Not every computer supports WOL at all, and the configuration is not normally done either by the computer manufacturer or the purchaser. It would be possible, I suppose, for the installation of the connector to configure the operating system correctly, but it's not really possible for the connector to change the BIOS configuration.

    Even if a computer is configured to support Wake On LAN, not every motherboard/BIOS does so in a useful fashion. There is hardware available which, if configured for WOL, will wake up to any network traffic. That sounds desirable, but in reality, such computers will generally be awakened by other random traffic on your LAN within a few minutes of being put into a power saving state.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, August 11, 2009 8:31 PM
    Moderator
  • Isn't there another way to acieve this effect, other than WOL? - I mean can't the console (remote access) send some kind of signal to the sleeping computer to wake up? I thought I saw some hack somewhere the you can send a code to the computer and wake it up... I'll look again...but, by whatever means, this seems retarded to me, to have the ability to remotely connect to your home PC but have no control what-so-ever if it's sleeping? Doesn't backup itself wake sleeping computers? Can't that same code be sent from a remote location?
    Tuesday, August 11, 2009 8:37 PM
  • If the home PC is off (standby, hibernation, hybrid sleep) how exactly do you propose to wake it, other than network traffic (i.e. Wake On LAN)?

    The "code" you're talking about is called a "magic packet", and it is a Wake On LAN packet.

    Backup wakes a sleeping computer using a hardware timer on the client computer. The server is a recipient of backup data, not a controller for when the backup starts. Even though you configure the backup window in the console, it's still managed locally.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, August 11, 2009 8:47 PM
    Moderator
  • I wonder if this would work - log in remotely to the WHS console change the time from default (12:00 AM) to something else that's closer to the current time... , You know something close to when you need to remotly connect to your home PC - like for instance, it's 4.48 PM my time now, so set the backup time to 5:00 PM - Would the computer wake up for backup and therefore I would be able to remotly connect??? So I will try this, but I'm wondering if there is a way to remotely change hours to minutes. you know,  wake up a sleeping computer backup time using minutes, right now it appears as though you can only change the hour.

     
    • Edited by pied piper Tuesday, August 11, 2009 8:57 PM
    Tuesday, August 11, 2009 8:53 PM
  • No, that won't work. The backup is run entirely from the client. The server only receives the data and, when asked by the client, provides information about the current setting of the backup window. If the client is asleep/hibernating, it will wake when the hardware timer in the client says to, no matter what you do to the backup window. There is nothing built into Windows Home Server (or Windows in general) that will wake a sleeping computer.


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, August 11, 2009 9:11 PM
    Moderator