Thanks all for your replies. I will try to descibe my situation a bit better.
- I have this server at home to share data, pictures and music. - I want the server to go down on order to save on the electricity bill and because of the noise the machine makes. - To wake the server up takes only seconds and as long as there is network activity directed to the server, it wont go down. That's why I am using the 1 minute time. - I am not always using the SB2. - I have two laptops and besides the server no other computer. If I switch one of them on, the server wakes and I can logon to the domain defined on the server. That way we can easily share all files and printers. If switched off the server goes to sleep automatically. So this all worked perfectly for months. Until I bought the SB2. Perfect machine but it keeps communicating with the server even if in standby mode. So the server won't go to sleep anymore. Why I don't like the administrator wake-on-lan option: - If I switch on one of the laptops and try to logon to the domain, no WOL (=magic packet) is send, so the server wouldn't wake and I cannot logon. - Apparently the administrator option on Server 2003 should not be used for this purpose because it automatically shuts itself down after 2 minutes. It's designed for administrator activities on the server. Why I don't like the slimserver and/or the remote control of the SB@ to take control of the wake/sleep state of my server by using scripts etc.: - because I am not always using the SB2. Hopefully it's more clear now what the problem is and why I want the SB2 to stop communicating with the server if in standby mode. As for your question: "Also can you tell me more about disabling Wake-On-Lan functionality in W2k03. If this fixes the sleep issue, it could provide Microsoft with the info required to create a patch for the problem I'm seeing. I currently have a call open with them and would like to provide more feedback." I am not an expert on Server 2003 but I did a lot of testing and can only tell you my findings and opinion. I have found out that while on normal wake-on-lan everything works fine. Waking and staying awake is no problem as long as there is network traffic directed to the server. So with the SB2 switched on it wakes and stays awake. If the administrator wake-on-lan option is ticked a magic package is needed to wake the server but then the server goes back to standby after two minutes if not used by an administrator. If I wake the server with the magic package and remotely log on using the standard remote administrator access of Server 2003, the server stays awake. This is also the case if you work directly on the computer. So my quess is that this option is designed for administrators to wake the server if shut down in case of problems and allow them to fix the problem. So not for end-users or end-user hardware like the SB2. Normal wake-on-lan should be used instead. What I still don't understand: why do we want the SB2 to send WOL packages (=magic package)? If normal network traffic directed to the slimserver computer also wakes it. Cheers, Reinoud -- reinoud _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
