No worries but it seems that communication is very difficult. Probably has to due with the fact that english isn't my mother tongue.
I selected Wake-on-link in the Bios. Server 2003 gives two power options for the network adapter. 1-allow this device to wake the computer. 2-only allow administrators to do this. I selected option 1 only. If I select option 2, the computer needs a magic package to wake. Also if I select option 2, the computer is showing the same problems as you describe, it only stays awake for 2 minutes. I still think we are having the same problem. You wrote: "may have been caused by a bug in the NIC driver I was using. I upgraded as part of my recent troubleshooting" I think it has only to do with your bios change and not with the upgrade you did. Switch back to "wake-on-lan" instead of "wake-on-link" and you will see "standby/wake/standby/wake" behaviour returns. you also wrote: "My PC will now sucessfully stay in standby with Wake on Link enabled" Yes, it stays awake because the SB2 keeps communication with it. Wake-on-link means 'network activity directed to the computer's ip address' and not 'network cable connected'. I quess that you now, with the 'wake-on-link' option selected, have trouble getting the computer to sleep. And that is because the SB2 is constantly communicating with your server. Switch the SB2 off and you will see the server goes to sleep automatically. Switch on the SB2 and your server wakes and stays awake. But I could be wrong and we could have a different problem. Reinoud -- reinoud _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
