Answered by:
Green icon but can't open Console or RDP.

Question
-
My WHS seems to funtion as expected but after a while I can't connect to the console even while the icon is green. RDP too will not connect. I went to check the machine directly and the attached display won't even show the desktop as if the machine was asleep and turns off. After a hard reset the WHS seems to operate normally until the next day.
I reinstalled WHS and the symptom still persists.
Monday, April 12, 2010 2:37 PM
Answers
-
After disabling Avast! to autoscan the issue is cleared up. Not a solution but a fix for now.
- Marked as answer by Win 6.9 Wednesday, April 14, 2010 2:40 PM
Wednesday, April 14, 2010 2:40 PM
All replies
-
Is this an OEM build or a bought server from say HP, Lenovo, Acer, etc?
--Monday, April 12, 2010 2:49 PM -
OEM - homegrown
The problem started late last week out of the blue, I haven't inkered with my server for the longest time (I pride WHS on the lack of need to mess with it), I reinstalled WHS in 'repair' fashion to no advantage.
Monday, April 12, 2010 2:54 PM -
I would say it's some kind of hardware problem - perhaps caused by the drying out of capacitors on the motherboard or in the CPU. Does running say something like memtest86 overnight work okay?
--- Proposed as answer by Al West Monday, April 12, 2010 5:12 PM
Monday, April 12, 2010 3:40 PM -
I haven't ran memtest but your theory holds merit as the board is getting old.Monday, April 12, 2010 4:08 PM
-
I meant anything else other than Windows Home Server that will cause some CPU utilisation - memtest is a good one as it should freeze with the total elapsed time on screen.
--Monday, April 12, 2010 5:12 PM -
Have you made any changes to your server since you reinstalled? Installed/uninstalled any add-ins? Installed software via the server desktop (either logged in directly or through Remote Desktop)? Changed anything in the operating system?
I'm not on the WHS team, I just post a lot. :)Monday, April 12, 2010 5:43 PMModerator -
The problem arose before I performed the re-install, in fact that was the reason for the re-install. I had made absolutely no changes to the server prior to this issue with the exception of a possible AnyDVD update, otherwise I tend to leave my WHS be.
The only anomaly I can think of was that the power had gone out recently but my WHS is connected to a UPS and I shut down the machine minutes after the power had gone out via the console from my laptop as my modem and router are also on battery back up.
Added: Prior to that I installed a 2TB a few weeks ago.
Monday, April 12, 2010 7:01 PM -
...
with the exception of a possible AnyDVD update
...
I'm not on the WHS team, I just post a lot. :)Tuesday, April 13, 2010 1:32 AMModerator -
I was able to turn on the monitor this morning to see a balloon that Avast! 4.8 has begun a system scan and any attempt to do anything like running task manager or restarting was futile. I went ahead and disabled scheduled scans too see if this is the culprit.
Assuming this fixes my issue I'll be content yet still a bit disturbed.
Tuesday, April 13, 2010 1:14 PM -
After disabling Avast! to autoscan the issue is cleared up. Not a solution but a fix for now.
- Marked as answer by Win 6.9 Wednesday, April 14, 2010 2:40 PM
Wednesday, April 14, 2010 2:40 PM -
This is one of the reasons why at every opportunity I say Avast is unsuitable for Headless Home Servers.
--Wednesday, April 14, 2010 4:15 PM -
This is one of the reasons why at every opportunity I say Avast is unsuitable for Headless Home Servers.
--lol.
Avast doesn't cause this problem on my servers. Including an EX475 that's never been upgraded. (Why bother? It does what I want and gives sufficient performance that I don't see a reason to complain.) It seems likely to me that the problem is not caused by Avast, though it may be exacerbated by it...
I'm not on the WHS team, I just post a lot. :)Wednesday, April 14, 2010 10:51 PMModerator