Home Server Possible Update Bug ? Console Password Incorrect error? RDP no longer functional?

• Question

• 

  

  0

  Sign in to vote

  Okay so I am posting this to find out more about the issue I have run into and see if there is a known bug or fix in the works.
  
  My recent experience with WHS has been unpleasant to say the least leaving me wanting to throw out the WHS software all together. Now don't get me wrong I had a WHS up and running months ago when the only available update was PP1 in beta and it worked great. Now however there seems to be a major bug in one or more of the updates currently out. Let me explain what has lead me to this conclusion.
  
  After parting out my original WHS months ago. Since I just built a new i7 to replace my existing system I used the parts from my Q6600 system to become the new home server.
  
  Hardware being used currently
  
  Intel Q6600 2.4GHz
  4GB DDR2 G-Skill 800MHz
  ASUS P5N7A-VM Motherboard (NV9300 onbaord)
  WHS OEM
  
  Now with that being established I will get into what i have run into how I attempted to fix it and how I finally got WHS working as it should.
  
  Initial install of WHS went as expected installed set up everything up and running. I used RDP from my main client machine to manage updates to PP1 so I could install console on x64 since I run Vista x64 I had to run updates to PP1 before being able to install WHS Console on any client machines. WHS found the PP1 plus 54 additional updates to install. Thinking nothing of this being an issue I install all the updates. After installation the WHS rebooted. Upon reboot I went through my standard network to access the share to pull down and install the new console. When I installed console the administrator password functioned and work without issue to install WHS console. When console finished install I attempted to log in to console to set up my user account for this client machine. This is when I found out a problem existed.
  
  Every time I attempted to log into console using my admin password I received error Password incorrect. So I attempted to remote back in using RDP. RDP no longer functioned giving me the cannot connect error.
  
  To trouble shoot I connect my monitor and peripherals to WHS directly log in using admin password everything seems to be working fine. I checked RDP settings good there, accessed console from within the home server directly working fine. I began looking at the network. I ping the router IP, Home server, Client 1, client 2. No packets lost no errors no issues. I then went to the client system 2 and attempt to set console and test RDP. Same issues happens on this client also.
  
  I then move to my router changing various settings to no avail. till i finally attempt to reset my router to default. With router on default no security I get the same error on both client machines.
  
  This is where i get into the nitty gritty
  Checked credentials / key manager permisions
  Checked component services on server / client 1, client 2 (DNS, TCP/IP, Workstation)
  Checked verified user names matching
  Checked verified workgroup all the same
  Added permissions to DCOM WHStransport component services
  Doug into the registry of client and server to no avail.
  Eliminated windows firewall to no avail.
  Attempted router port forwarded and opening and so on.
  And more.
  
  So I finally at this point decide I will reinstall using the WHS disk. I reinstall and once complete RDP and console same issue still not fixed.
  
  This leads me to one last ditch effort to find out what is going on. This is where i do a new install complete fresh delete of all shares and WHS files install. NOT A REINSTALL a new install. Check RDP is now working decide to do the all 55 updates again. Same problem begins RDP stops working after it initially was working, Console incorrect password error all over again.
  
  I then do the NEW install again complete wipe and install. RDP again works. This time I manually download only PP1 update and install reboot. RDP is still working at this point on both client systems. I then pull the latest console over and install it. Install goes smoothly admin password working as usually. Run console on both clients to connect and admin password now works.
  
  This means one or more of the 55 updates excluding PP1 is causing the issue.
  
  That is the whole ordeal. :) But I am now working I just can't update lol.
  
  Any suggestions would be much appreciated. Any questions feel free to ask.
  
  

  Sunday, May 10, 2009 10:37 PM