none
The password is incorrect on WHS consolle & Remote Desktop does not work.

    Question

  • OK now, I have read a lot of post for this issue; I have read all and tested all the solution inside...

     

    Not any of this as worked for my

     

    The base condiction is this:

    a 1 installation off a WHS in demo (30 day) mode then a litle "but working" thest on a windows 2003 for smal office, then the decision to buy the WHS.. ( the 2003 is to expensive for my budged)

     

    at the end a complety new server PC whit OEM version of WHS.. whit the same 2x XPPro client used before..

     

    Same net, same router,same client, same internet connection, same cable :-)

     

    the 1 time WHS vorked fine the second time i see it files from "workgroup" but i can, no more, reach it by REMOTE DESKTOP and WINDOWS HOME SERVER CONSOLE.

     

    BUT the WHS Back UP work fine ! i read & write the Shared folder from WHS i read and write "Client shared folder" from the WHS servers.. so .. i think it is NOT a network problem.

     

    Now thew solution i have tested:

    1 Tested the wired cable :-)

    2 Tested the password case :-) ( i ave only "one" for all my PC at the moment)

    3 Tested Folder and file full permissione followind this post (by nigelbb in  http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1922353&SiteID=50) > -  I don't even see anything in the folder

     

    4 Tested rundll32.exe keymgr.dll, KRShowKeyMgr, foolowind this other post

    (by dmxrob in http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2284855&SiteID=50) but - after typing that in I don't even see anything in the Stored User Names and Passwords window.

     

    5 tested if  they are in the admin group

    6 Individual permissions are good too

    7 i log in my server from intranet http://192.168.1.10/ all ok ( for file sharing )  BUT NOT when i use "Connect to your Home Server" to Remote Access to Windows Home Server Console link.. a this point i write the Server password and then the windows retourn to https://192.168.1.10/remote/admin.aspx? .. i think.. the password it is not recognized anymore..

    8 at the end i have used the Connetor troubleshooter whit this problem:

    1-Two or more network adapters are active ?????

    2-Cannot connect to the server internal Web site (password hint page)

    3-Cannot connect to the server internal Web site (simple page)

    4-No DHCP server, or DHCP server is not reachable ?????

    5-More than one IP address...????

     

    -If you  say; "No problem reinstall the client ad all goes ok..."  i make it .. but.. it is a solution ? 

    -Why i cannot reach Remote Access to Windows Home Server Console fron my intranet ?  

    -Why i can no more  access my WHS server from the Remote desktop ( this is mandatory for my situation i need the server away form my desk!)

     

    Tanks for any reponse..

    Ave a nice day d'8-D

    Wednesday, March 26, 2008 11:21 AM

Answers

  •  

    I  have reinstalling from scrarch the SERVER but NOT updating whit
    Nothing
     
    all. is ok now 
     
    The "client side" now work beautifull whitout the need of reinstalling..
     
     Remote desktop connetor, and Home server consolle work fine..
     
    so... now the problem is what updating I can make...and what not.. but this i test day by day.. now i shoul make other things than look a "copy bar" running..
     
    Thanks to all people that at give attention on this thread.. syl 
    Saturday, April 12, 2008 4:52 PM
  •  brubber wrote:

    Glad to hear you fixed it! I somehow lost track of this thread, sorry for that.

     

    Concerning the updates, AFAIK you can always uninstall them individually. From a security point of view I would strongly advise you to apply all updates.

     

    he he he my fault Brubber i have open anoter thread

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=3082852&SiteID=50

     

    ad now closed all togheder,

     

    but now I install "one by one the" the security update...why the uninstall procedure does not have helped

     

    Myby the problem is another... and reistalling from schacht at solved it.. 

     

    Anyway Thanks for your attention See you next time :-) 

    Sunday, April 13, 2008 3:21 PM

All replies

  • Possibly the actual login name and the displayed username on the client don't match.

     

    To check this on the client machine do: Start, Run, type control userpasswords2 and hit Enter. This will open a window that shows the actual login names. If you select a user you and click properties you will see the loginname and also the displayed name. The name of the WHS account should match the actual loginname (or the other way around, whichever you like best)

    Wednesday, March 26, 2008 11:28 AM
    Moderator
  •  

    OK This solution i have read too... No, i'm sorry the name is the same.. but i can "reset" the password for the local account..

     

    Only i make 1st a local bk for my data.. window say if i reset the password i can lose some information

     

    i test this in the next 4h

     

    But.. what concern this whit the "remote desktop" and the "double ip" problem ? i thing is in "this" way we should find the solution...  

     

    Anyway thanks for the answer.. :-)

    Wednesday, March 26, 2008 12:59 PM
  •  Sorry I didn't read your first post more accurately. My answer was based on your post subject and the two "password" problems you mentioned.

     

    So:

     

    1. Remote access to the WHS console trough the Windows Homeserver Remote access webpage is not possible when you connect from within your LAN using private IP-address. If your router supports it access from https://yourserver.homeserver.com could work if you have remote access setup.

    If you want to test remote access you can best try this from outside your LAN

     

    2. To logon to the WHS console from a client use the tray icon, logon using Administrator password

    3. If you want RDP (remote desktop access):

    a. On a client do Start, Run, type mstsc.exe and Hit Enter

    b. In computer field type servername or IP-address

    c. Logon using username = Administrator, password = WHS Administrator password

     

    Two or more network adapters could arise from a firewire port or a "virtual" adapter (for example to accomodate VPN access to another server). Normally this should not be a problem. DHCP server not reachable is also a common message which is not necessarily a problem. If all of your systems have proper IP-address, gateway and DNS server don't worry about this message.

     

    The cannot connect to the server internalWeb site message are often related to incorrect DNS server settings. In general (not always though) primary DNS should point to your router, and NOT to an external address. You can either set this manually on your clients, or in DHCP config of your router.

    Wednesday, March 26, 2008 2:08 PM
    Moderator
  • NP.. i see you have a lot of work.. but

     

    For the 1st point..  i say "haaaaaaaa" and i go to tomorrow to my bruder to test.. :-)

     

    For the 2st point.. ok i now how to start remote connection :-p and i Logon using username = Administrator, password = WHS Administrator password and the right IP (manual set)  but the answer is the same. the remote computer is it unreachable.. contanct the hover (me) ort the net admin ( me too) he he he...

     

    For the 3st point i should investigate: a this moment i have set it manualy ( i now a little ow it works) but the DNS sound the point to look about.. 

     

    I make this and replay later..

     

    Thank Brubber..

    Wednesday, March 26, 2008 3:25 PM
  •  DOD63 wrote:
    NP.. i see you have a lot of work..

     

    It's not work for me, I'm not in computer business. It's just for fun and to tickle my brain.

    Thursday, March 27, 2008 12:18 AM
    Moderator
  •  brubber wrote:

    It's not work for me, I'm not in computer business. It's just for fun and to tickle my brain.

     

    WOW this make you a PALADIN ! my respect for you

     

    But.. my problem stil remain i have in the order:

     

    1-Verified the DNS.. .. notting new append

     two word about... wen I instal a Win03 Server whit "domain" i set the DNS & the DHCP and the WINS on this PC (192.168.1.10) and the router (ADSL) (192.168.1.5) now the WHS does not ave a Domain but it is same a 2003server machine

    myby i should install the DNS on the WHS PC ?? i can make this but you thingh this help ?

     

    2-Changed the WHS server name.. notting new append

    Mhhhhhhh myby i should change the WHS IP ?

     

    3- whit control userpasswords2 i have RESET the password of my profile.... notting new append

    Myby create a new user profile can help ?

     

    OK I d'ont Have other IDEA

     

    the 1st problem is the fact that altrought i can seee and map & use the shared partition from the WHS i cannot reach it whit the mstsc.exe

    This problem rest the MANDATORY PROBLEM I need to leave the WHS server from under my desk.. i cannot slepp whit him Stick out tongue

     

    Thanks for any reponse

Thursday, March 27, 2008 10:23 PM
  •  

    I  have reinstalling from scrarch the SERVER but NOT updating whit
    Nothing
     
    all. is ok now 
     
    The "client side" now work beautifull whitout the need of reinstalling..
     
     Remote desktop connetor, and Home server consolle work fine..
     
    so... now the problem is what updating I can make...and what not.. but this i test day by day.. now i shoul make other things than look a "copy bar" running..
     
    Thanks to all people that at give attention on this thread.. syl 
    Saturday, April 12, 2008 4:52 PM
  • Glad to hear you fixed it! I somehow lost track of this thread, sorry for that.

     

    Concerning the updates, AFAIK you can always uninstall them individually. From a security point of view I would strongly advise you to apply all updates.

    Sunday, April 13, 2008 3:55 AM
    Moderator
  •  brubber wrote:

    Glad to hear you fixed it! I somehow lost track of this thread, sorry for that.

     

    Concerning the updates, AFAIK you can always uninstall them individually. From a security point of view I would strongly advise you to apply all updates.

     

    he he he my fault Brubber i have open anoter thread

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=3082852&SiteID=50

     

    ad now closed all togheder,

     

    but now I install "one by one the" the security update...why the uninstall procedure does not have helped

     

    Myby the problem is another... and reistalling from schacht at solved it.. 

     

    Anyway Thanks for your attention See you next time :-) 

    Sunday, April 13, 2008 3:21 PM
  •  brubber wrote:

    Glad to hear you fixed it! I somehow lost track of this thread, sorry for that.

     

    Concerning the updates, AFAIK you can always uninstall them individually. From a security point of view I would strongly advise you to apply all updates.

     

    he he he my fault Brubber i have open anoter thread

    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=3082852&SiteID=50

     

    ad now closed all togheder,

     

    but now I install "one by one the" the security update...why the uninstall procedure does not have helped

     

    Myby the problem is another... and reistalling from schacht at solved it.. 

     

    Anyway Thanks for your attention See you next time :-) 

    Sunday, April 13, 2008 3:21 PM
  •  DOD63 wrote:

    but now I install "one by one the" the security update...

     

    To be fair, As promised I installed all update Higt Priority (express) one at a time ..

     

    All work !!  Then regarding my problems I can safely make the automatic update


    for this optional update I am not going to try ..
    -Group Policy Preference Client Side Extensions for Windows Server 2003 (KB943729)
    -Microsoft .NET Framework 3.0: x86 (KB928416)
    -Remote Desktop Connection (Terminal Services Client 6.0) for Windows Server 2003 (KB925876)

     

    I see over my share of unofficial betatester, and the next time rather than buying a software microsoft before first sevice pack: I will be my hand cut out..  :-)

     

    Saturday, April 19, 2008 8:31 AM
  • I had exactly the same problems following the recent Jan '09 WHS updates when trying to connect to my WHS through WHS console and RDC.  Below is how I fixed the problem;

    I found the solution to my problem when googling the error message

    '\SystemRoot\System32\RDPDD.dll failed to load'

    that I was seeing under the System entry in Event Viewer on my WHS

    From the information on the webpages

    http://blogs.technet.com/brad_rutkowski/archive/2008/01/04/systemroot-system32-rdpdd-dll-failed-to-load.aspx


    http://forums.nvidia.com/index.php?showtopic=67147&hl=remote desktop&st=60

    I implemented the following fix;
     
    Open up regedit on your WHS and add the following SessionImageSize DWORD Value in;

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
    Value Name 'SessionImageSize'
    Value data '00000020'

    Other posts on the nVidia forum above have reported that 32 MB didn't work for them but by increasing the size (Value data setting) of the sessionimagesize they overcame the problem.

    00000020 = 32MB
    00000040 = 64MB
    00000060 = 96MB
    00000080 = 128MB

    Although this problem is linked to my WHS having onboard graphics it could occur for others as the root of the problem lies with the WHS session image space being too small, which I believe prevents it from loading any more drivers into it when programs such as RDC request this.  Items which typically share the session image space are display driver drivers, printer drivers and of note, the remote desktop protocol display driver.

    Following the above fix I decided to see if it was perhaps down to a nVidia driver issue as I was using drivers from Jan 2008 (listed as 6.14.11.7123 in Device Manager Properties) and the solution was originally posted in nVidia forums.  I removed the SessionImageSize entry from my WHS registry, rebooted the server and installed the latest nVidia drivers (v181.22, listed as 6.14.11.8122 in Device Manager Properties).  Following the required reboot I found that the problems connecting to WHS through either the WHS console or remote desktop did not return.  Just out of interest I decided to have a look in the registry and low and behold there was now a SessionImageSize entry with a value of 00000010 (16MB). 

    I hope that the above solves the issues that you were having and you can now apply all the updates to your WHS without any further problems.

    Yak.
    ====
    WHS Specs:
    AMD Athlon 4850e
    Asus M3N78-EMH (with onboard nVidia 8200 graphics)
    3GB Ram
    4 x 1 TB Samsung hard drives (HD103UJ)
    1 x 320 GB Hitachi hard drive (HDP72503)

    • Proposed as answer by Yakelaen Saturday, January 31, 2009 9:47 PM
    Saturday, January 31, 2009 9:41 PM
  • I experienced the same problem after the latest patch (Feb 09).  I upgraded my graphics driver as the above poster suggested and everything is back to normal.
    Monday, May 04, 2009 5:03 PM