Answered by:
Login error: "The password is incorrect. Please retype your passowrd. Letters in passwords must be typed using the correct case."

Question
-
When trying to login to the WHS Console from a client machine (any client machine on my network), I get this error:
"The password is incorrect. Please retype your passowrd. Letters in passwords must be typed using the correct case."
This error shows up on both XP and Vista clients and therefore I am unable to logon to the Console.
I have tried the 3 suggestions of these thread, but they did not solve my problem:
http://social.microsoft.com/Forums/en-US/whssoftware/thread/5778781c-5d0d-4df4-ad74-8962fd449f16/
Obviously there is something I'm missing. Thanks for any assistance that you can provide.Sunday, November 16, 2008 10:03 PM
Answers
-
Hi,
is the server a headless system (no VGA out)?
If yes, reinstall seems to be your only option, if a reboot doesn't fix the behavior.
Otherweise login locally and check the event log for error messages and warnings regarding DCOM, authentication and RDP related informations.
Port forwarding is only important, if you try to access WHS from outside of the local subnet. (In this case at least for the Remotedesktop exception the scope of the Windows Firewall on the server needs to be changed to allow access from other networks.)
Did you install any 3rd party software on the server before this happened?
Best greetings from Germany
Olaf- Marked as answer by plasticq Monday, November 17, 2008 5:39 AM
Monday, November 17, 2008 5:15 AMModerator -
Olaf Engelke said:
Hi,
is the server a headless system (no VGA out)?
If yes, reinstall seems to be your only option, if a reboot doesn't fix the behavior.
Otherweise login locally and check the event log for error messages and warnings regarding DCOM, authentication and RDP related informations.
Port forwarding is only important, if you try to access WHS from outside of the local subnet. (In this case at least for the Remotedesktop exception the scope of the Windows Firewall on the server needs to be changed to allow access from other networks.)
Did you install any 3rd party software on the server before this happened?
Best greetings from Germany
Olaf
Thanks Olaf -- as I face-palm. Didn't even think to check the event viewer as I figured it was a network issue that I was overlooking. Ok, so let me include the error as spelled out in the Event Viewer so others who have this issue might find a solution:
I logged directly into the system, then went to -- Start button | Control Panel | Administrative Tools | Event Viewer -- In the Event Viewer window, under the System root, there were a handful of events that had time-stamps that matched when I would try to connect to the system via Remote Desktop. The text of these events is..."Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
Did a search for this error and came across this:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp"
http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx
Which includes several options to fix this. The fix that worked for me was adding a key to the Registry... to quote from the link above:A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)
It's a registry fix that increases the size of the session image space. Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Where 00000020 is hex for 32
Rebooted and I can now remote into the system from my clients AND I can now start the Windows Home Server Console from my clients as well and no longer get the "... password is incorrect. Please retype..." error I had been getting.
Cheers! and many thanks for the assistance.
Monday, November 17, 2008 5:53 AM
All replies
-
plasticq said:
When trying to login to the WHS Console from a client machine (any client machine on my network), I get this error:
"The password is incorrect. Please retype your passowrd. Letters in passwords must be typed using the correct case."
This error shows up on both XP and Vista clients and therefore I am unable to logon to the Console.
I have tried the 3 suggestions of these thread, but they did not solve my problem:
http://social.microsoft.com/Forums/en-US/whssoftware/thread/5778781c-5d0d-4df4-ad74-8962fd449f16/
Obviously there is something I'm missing. Thanks for any assistance that you can provide.
Are you using the server password (not a password for a user you created)? Were you ever able to access the Console? Have you tried logging into the server desktop (using Administrator as the user and the same password for the password)?Sunday, November 16, 2008 10:27 PMModerator -
kariya21 said:Are you using the server password (not a password for a user you created)? Were you ever able to access the Console? Have you tried logging into the server desktop (using Administrator as the user and the same password for the password)?
Yes, I'm using the Admin password for the server. No, I have never been able to access the Console from any client. Not sure I understand your 3rd question -- when sitting in front of the server, I can and do log into it using "Administrator" as the user and using the Admin password and it logs me in fine.
Also, this may not be of any assistance (but it might) -- while logged directly into the server (sitting in front if it) and while in the Console, via the ASoft AutoExit plugin, I can use Remote Desktop to access the desktops of any system on my network -- but I can't get my clients to Remote Desktop into the Server (to control the server).Sunday, November 16, 2008 10:38 PM -
plasticq said:
Yes, I'm using the Admin password for the server. No, I have never been able to access the Console from any client. Not sure I understand your 3rd question -- when sitting in front of the server, I can and do log into it using "Administrator" as the user and using the Admin password and it logs me in fine.
Also, this may not be of any assistance (but it might) -- while logged directly into the server (sitting in front if it) and while in the Console, via the ASoft AutoExit plugin, I can use Remote Desktop to access the desktops of any system on my network -- but I can't get my clients to Remote Desktop into the Server (to control the server).
What firewall(s) do you have on your clients? Did you install any additional firewall on the server? Have you tried completely disabling all firewalls on a client and the server at the same time?- Edited by kariya21Moderator Sunday, November 16, 2008 11:02 PM clean up
Sunday, November 16, 2008 11:01 PMModerator -
kariya21 said: What firewall(s) do you have on your clients? Did you install any additional firewall on the server? Have you tried completely disabling all firewalls on a client and the server at the same time?
No extra firewall software installed and Windows firewall for both/all systems is disabled. Only AV application running is AVIRA free edition. Also, I tried connecting via Remote Desktop with port 3389 forwarded to the server through my router -- tried connecting w/ the port forward enabled and disabled -- and no connection either way.
Also, I can ping the server from client PC's and I can access the WHS folder shares from client PC's and WHS is backing up the client PC's without any issues.Sunday, November 16, 2008 11:42 PM -
plasticq said: No extra firewall software installed and Windows firewall for both/all systems is disabled. Only AV application running is AVIRA free edition. Also, I tried connecting via Remote Desktop with port 3389 forwarded to the server through my router -- tried connecting w/ the port forward enabled and disabled -- and no connection either way.
Also, I can ping the server from client PC's and I can access the WHS folder shares from client PC's and WHS is backing up the client PC's without any issues.
Never heard of AVIRA. Is that installed on your server? If so, you should only use A/V apps specifically designed for WHS. You might try uninstalling it (if it's on the server). Also, you might try breaking the connection between the modem and the router (in case your clients are going out to the internet). If neither of those work, the only suggestion I have left is Server Reinstallation.- Edited by kariya21Moderator Monday, November 17, 2008 1:33 AM clean up
Monday, November 17, 2008 1:31 AMModerator -
kariya21 said: Never heard of AVIRA. Is that installed on your server? If so, you should only use A/V apps specifically designed for WHS. You might try uninstalling it (if it's on the server). Also, you might try breaking the connection between the modem and the router (in case your clients are going out to the internet). If neither of those work, the only suggestion I have left is Server Reinstallation.
AVIRA is the antivirus app that I use on my clients (it is a rather popular AV application given its small footprint and lack of cost). It isn't installed on my WHS.
And I was expecting the suggestion for reinstalling the OS... ugh. Quite the common requirement for Microsoft OS's... when in doubt, reinstall.
Ok, now that I've got my mind acceptable to reinstalling... what is the best way to go about it so I don't lose my data?
And many thanks for the help you've provided thus far, it is appriciated.Monday, November 17, 2008 4:26 AM -
Hi,
is the server a headless system (no VGA out)?
If yes, reinstall seems to be your only option, if a reboot doesn't fix the behavior.
Otherweise login locally and check the event log for error messages and warnings regarding DCOM, authentication and RDP related informations.
Port forwarding is only important, if you try to access WHS from outside of the local subnet. (In this case at least for the Remotedesktop exception the scope of the Windows Firewall on the server needs to be changed to allow access from other networks.)
Did you install any 3rd party software on the server before this happened?
Best greetings from Germany
Olaf- Marked as answer by plasticq Monday, November 17, 2008 5:39 AM
Monday, November 17, 2008 5:15 AMModerator -
Olaf Engelke said:
Hi,
is the server a headless system (no VGA out)?
If yes, reinstall seems to be your only option, if a reboot doesn't fix the behavior.
Otherweise login locally and check the event log for error messages and warnings regarding DCOM, authentication and RDP related informations.
Port forwarding is only important, if you try to access WHS from outside of the local subnet. (In this case at least for the Remotedesktop exception the scope of the Windows Firewall on the server needs to be changed to allow access from other networks.)
Did you install any 3rd party software on the server before this happened?
Best greetings from Germany
Olaf
Thanks Olaf -- as I face-palm. Didn't even think to check the event viewer as I figured it was a network issue that I was overlooking. Ok, so let me include the error as spelled out in the Event Viewer so others who have this issue might find a solution:
I logged directly into the system, then went to -- Start button | Control Panel | Administrative Tools | Event Viewer -- In the Event Viewer window, under the System root, there were a handful of events that had time-stamps that matched when I would try to connect to the system via Remote Desktop. The text of these events is..."Application popup: : \SystemRoot\System32\RDPDD.dll failed to load
Did a search for this error and came across this:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp"
http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx
Which includes several options to fix this. The fix that worked for me was adding a key to the Registry... to quote from the link above:A solution found at http://forums.nvidia.com/index.php?showtopic=67147&hl=remote%20desktop&st=60 worked for me (and others.)
It's a registry fix that increases the size of the session image space. Add the following key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"SessionImageSize"=dword:00000020
Where 00000020 is hex for 32
Rebooted and I can now remote into the system from my clients AND I can now start the Windows Home Server Console from my clients as well and no longer get the "... password is incorrect. Please retype..." error I had been getting.
Cheers! and many thanks for the assistance.
Monday, November 17, 2008 5:53 AM