How to fix share access issues where user name and password are requestedSometimes, you will install the connector on a PC, create a user on Windows Home Server that matches the user you're logged in as locally, and yet you get asked for a user name and password when you try to view a share on the server. This may occur because Windows distinguishes between the <span style="font-style:italic">user name</span> and the <span style="font-style:italic">display name</span>. The <span style="font-style:italic">display name</span> is what's shown on the logon screen on the client, or in the standard User Accounts applet in Control Panel. The <span style="font-style:italic">user name</span> is the actual user that logs in. Sometimes, particularly on PCs from OEMs, there will be a default account when the computer is set up, and that account's <span style="font-style:italic">display name</span> will be changed as part of setup. Changing the <span style="font-style:italic">display name</span> doesn't affect the <span style="font-style:italic">user name</span>, however, and it's the <span style="font-style:italic">user name</span> that Windows Home Server uses to authenticate.<br><br>You'll need to inspect the user names in the Advanced User Accounts Control Panel. On the client that's not connecting successfully:<br> <ul> <li>Start → Run → type 'control userpasswords2' → press Enter. <li>If you are using Windows Vista and have UAC turned on, there will be a confirmation prompt. Confirm that you want to do this and continue.<br> <li>There will be one or more user names listed. Probably none of them will match the user you think you're logged in as. You can find out who you are actually logged in as by running the command <font style="font-weight:bold;color:rgb(128,0,0)" size=2><span style="font-family:Courier">echo %username%</span></font> in a DOS command prompt.<br> <li>Find the user that was returned from the DOS command above, or select each user in turn and click on the Properties button. You will find that one user will show a 'Full Name' that matches who you think you're logged in as. Change that user's 'User Name' to match the <span style="font-style:italic">logon name</span> of the appropriate user on Windows Home Server.</li></ul>The Advanced User Accounts Control Panel is not the only interface available in Windows for changing the user name, but it's the most straightforward. You can safely change the user name without causing any problems; the display name will remain associated with it, as will any files or folders that are owned, etc.© 2009 Microsoft Corporation. All rights reserved.Tue, 02 Sep 2008 21:30:58 Zdeff41ae-f363-4fd5-a51f-6043b79ac695http://social.microsoft.com/Forums/en-US/whsfaq/thread/deff41ae-f363-4fd5-a51f-6043b79ac695#deff41ae-f363-4fd5-a51f-6043b79ac695http://social.microsoft.com/Forums/en-US/whsfaq/thread/deff41ae-f363-4fd5-a51f-6043b79ac695#deff41ae-f363-4fd5-a51f-6043b79ac695Ken Warrenhttp://social.microsoft.com/Profile/en-US/?user=Ken%20WarrenHow to fix share access issues where user name and password are requestedSometimes, you will install the connector on a PC, create a user on Windows Home Server that matches the user you're logged in as locally, and yet you get asked for a user name and password when you try to view a share on the server. This may occur because Windows distinguishes between the <span style="font-style:italic">user name</span> and the <span style="font-style:italic">display name</span>. The <span style="font-style:italic">display name</span> is what's shown on the logon screen on the client, or in the standard User Accounts applet in Control Panel. The <span style="font-style:italic">user name</span> is the actual user that logs in. Sometimes, particularly on PCs from OEMs, there will be a default account when the computer is set up, and that account's <span style="font-style:italic">display name</span> will be changed as part of setup. Changing the <span style="font-style:italic">display name</span> doesn't affect the <span style="font-style:italic">user name</span>, however, and it's the <span style="font-style:italic">user name</span> that Windows Home Server uses to authenticate.<br><br>You'll need to inspect the user names in the Advanced User Accounts Control Panel. On the client that's not connecting successfully:<br> <ul> <li>Start → Run → type 'control userpasswords2' → press Enter. <li>If you are using Windows Vista and have UAC turned on, there will be a confirmation prompt. Confirm that you want to do this and continue.<br> <li>There will be one or more user names listed. Probably none of them will match the user you think you're logged in as. You can find out who you are actually logged in as by running the command <font style="font-weight:bold;color:rgb(128,0,0)" size=2><span style="font-family:Courier">echo %username%</span></font> in a DOS command prompt.<br> <li>Find the user that was returned from the DOS command above, or select each user in turn and click on the Properties button. You will find that one user will show a 'Full Name' that matches who you think you're logged in as. Change that user's 'User Name' to match the <span style="font-style:italic">logon name</span> of the appropriate user on Windows Home Server.</li></ul>The Advanced User Accounts Control Panel is not the only interface available in Windows for changing the user name, but it's the most straightforward. You can safely change the user name without causing any problems; the display name will remain associated with it, as will any files or folders that are owned, etc.Sun, 03 Aug 2008 13:54:09 Z2008-08-21T21:33:18Z