Can't connect via Server Console or Remote Desktop

[blin]

Prior to last night, I was able to connect to my home server by the server console or the remote desktop from any of the 4 computers and never had any problems. I can still access the shares and add/delete/move data within those shares but when I try to connect to the server, it says the server is not available. I first thought it might be the computer I was using so I tried another and then another and got the same results. I finally hooked my home server up to a monitor in hopes of there being something obvious that was causing the problem but that wasn't the case and it booted up without a problem.

When I log on locally to the home server, I use the administrator account and password just like I did in server console or remote desktop. Since I wasn't connecting to the server via console or remote, I tried to reinstall the connector software but it came back and said it didn't see the server. The only thing that changed was the updates I downloaded last night from MS.



Suggestions???

[blin]

How did you download the updates? Through the Console or through Internet Explorer?

[blin]

The updates were done through the console for the home server (I had actually forgotten about those and initially meant the updates to the 4 other computer and not the home server). The updates to the computers were done first and then I noticed that I couldn't connect via console or remote from any of the computers so I logged on locally to the home server and downloaded the updates for the server. After rebooting all computers (server included), I still couldn't connect via console or remote.

[blin]

I am having the exact same problem (glad that I am not the only one). I have a simple set up. A WHS, one vista pc and one xp pc. Everything was running smoothly, I set up the WHS and network at a house that I was house sitting for a couple of weeks. Then I unplug everything and go back home and set up the network (server and all) and now it does not work! Both client PCs can access the shared folders, but can not remote desktop or use the WHS connector software. I tried reinstalling the WHS connector client on the Vista pc, but after it finds the Server and I enter the password, it says that it can not connect. I downloaded the WHS tookit and ran it. The results stated that I would most likely have to reinstall the WHS operating system and I did, still have the same issue. I can't connect via console or remote desktop, but I can see the network drives ok. Does anyone know how to solve this issue? I have put about 12 hours into fixing this and all that I have is blood shot eyes and a girlfriend that is starting to think I am neglecting her.

[blin]

I've experienced the same problem. Mine is a simple setup as well. A WHS, one Vista Ultimate PC and one Vista Home Premium laptop. Everything was working fine and now nothing works. First I attempted a Server Reinstallation and that didn't work. Then I tried New Installation to see if that would solve the problem and it didn't work either. The only place that I can see the Shares is in Windows Explorer. When I try to install the connector software (either from the CD or via the Shared Software folder, it gets as far as entering the password (which tells me it in fact did find the server and apparently made some type of connection to it) and then comes back with the message that it can't connect and the same thing happens with Remote Desktop. I ran the WHS toolkit and submitted the error report via the tool included with it. The CAB number is 453277213.



Since the WHS was set on Automatic updates I can only presume that it downloaded and installed some update that basically crippled WHS. I saw somewhere that there was a problem with the .NET 2.0 SP1 that caused some serious problems but I checked the error logs and now all the services seem to be starting as they should. It was bad enough I had to waste the entire week transferring what turned out to be a bunch of corrupted files (yet another WHS bug that was reported by me during the beta testing but was apparently ignored and closed since it wasn't "reproduceable") to an external drive on my PC just to try and save what I could before doing the New Installation of WHS just to have things remain the same despite a week of trying to get it all to work again. What did Microsoft do this time that suddenly caused WHS to stop working overnight? Once again Automatic Updates causes more problems than it should.



Please tell me that there is a solution to this serious problem.

[blin]

I'm not sure if I have the same issue BUT things have been fine until the last set of Auto Updates on the server. In my case, the QSM service will not run and that means the Console will not start at all.



I have posted my details yesterday on this thread.



http://forums.microsoft.com/WindowsHome ... &SiteID=50



I am really not looking forward to re-installing yet again. I have over 250 GB of real data. I do have it backed up outside of the WHS.



I hope the recent updates have had some impact and that a recovery strategy can be found.

[blin]

After reading of your pain I then went to my WHS via remote and saw the update waiting to be installed. As you can tell, I have them downloaded but not installed. Attached was a KB article describing the only true update. It sounds like it may play a role in your problems so thought I would post it here:
http://support.microsoft.com/kb/948496