5 replies to this topic

[ubergeek101]

I have two routers in my setup. I have an e4200 as my primary router and an e3000 as my secondary router. The e4200 has stock firmware, but the e3000 has dd-wrt. The e3000 is connected to the e4200 as a wireless repeater bridge using the 5ghz band. Both routers advertise the 2.4ghz bands for wireless connections. My WHS 2011 server is hardwired to the e4200. I have a client machine that connects wireless to the 2.4ghz band on the e3000. Whenever this client is shutdown, lights out will still show it as active and the server never hibernates. I am using 1.5.2.1737. I have uninstalled and reinstalled and still have the issue. I had this same problem with 1.5.1.1656. The version before that had the problem as well, but you could tell by looking at the server that lights out was confusing this machine with the repeater bridge as well as other clients attached to it. Currently, when I look at the server it seems that lights out has detected the machine properly. However, it still doesn't detect when it is no longer active on the network.

Any help you can provide with this issue is appreciated!

[oj88]

Maybe the e3000 is somehow caching the connection. As an experiment, try to turn off the e3000 and see if LO will correctly tag the clients behind the wireless bridge as being shutdown.

[Tinus]

You have to assign the new router flag to the e3000: http://www.homeserve..._properties.htm (item 2).
Is that computer behind the e3000 added as ip based device or with WHS Connector? If it's an ip based device, then delete it in Lights-Out and add it manually again with fixed IP.

P.S. Moved to 2011 forum.

[ubergeek101]

The client on the E3000 is an XP machine added with the WHS connector. I found today that my problem may not be lights-out. Yes, lights-out does show the client active even after it is shutdown/hibernated, but it also shows active in the computers and backup tab. I did already have the E3000 added with the router flag checked. I deleted and it and redid it just for good measure. I have also uninstalled and re-installed the WHS connector. I am not really sure what else I can do at this point.

[Tinus]

That's a known bug in WHS 2011: https://connect.micr...-been-shut-down

The only workaround is a restart of the "Windows Server Health Service" (HealthAlertSvc).

If this happens repeatedly then create a small batch file with:

net stop HealthAlertsSvc
net start HealthAlertsSvc

Add a scheduled task to Windows task scheduler which runs that batch file every 1h.

[ubergeek101]

That did the trick. I will create the batch file as it happens every time this machine is booted. Hopefully this workaround will work until Microsoft actually fixes the problem. Thanks for the help!