locked
"No Access" on Shares RRS feed

  • Question

  • Something happened, and I have lost Access to my shares.

    The question boils down to this: How do I make sure that the Client sends the correct Username/Password combination to the server.

    If I try to open a share, I get "No Access"

    There are some very clear symptoms that tell me that the 'cached' Username/Password are not being sent by the XP Client to the WHS

    a) Guest access works on all shares. It I turn on 'Guest', connections are enabled. So WHS is working.
    b) Remote Access works. If I go to the 'homeserver' website for the server, I can login
    and browse the shares with the same userneme/pwd combo that I use on the XP client.
    c) Cycling through 'Net Use' enables access from the workstation:
       - (Step 1) NET USE shows a connected WHS share, the one that 'failed' to allow access initially when I checked the share. Use the /Delete switch to remove it.
       - (Step 2) Map the same share (via My Networks) and tell it to use a specific UserID/pwd (using the same as the logon UserID and account pwd) maps the share correctly, and ALL shares come alive.
       - Disconnnecting the manually mapped share causes all access to all shares be lost again.

    So although I am using the SAME UserID and password on all the alternate attempts as the initial logon to the workstation, only the workstation on it's own fails.

    Tried the following:
    a) Deleted and recreated User on WHS.
    b) Reset password on Client
    c) Reinstalled WHS connector.

    Any ideas as to why the UserID/Pwd that I use to logon to the workstation is not being sent to WHS. but if I send it manually it works fine?


    Friday, August 1, 2008 2:18 AM

Answers

  • You'll need to inspect the user names in the Advanced User Accounts Control Panel. On the client that's not connecting successfully:
    • Start → Run → type 'control userpasswords2' → press Enter.
    • There will be one or more user names listed. Probably none of them will match the user you think you're logged in as.
    • 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 be the same as the 'Full Name', which should match a user on Windows Home Server.
    This occurs because Windows distinguishes between the user name and the display name. The display name is what's shown on the logon screen. The user name is that actual user that logs in. 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.
    Friday, August 1, 2008 2:58 AM
    Moderator

All replies

  • You'll need to inspect the user names in the Advanced User Accounts Control Panel. On the client that's not connecting successfully:
    • Start → Run → type 'control userpasswords2' → press Enter.
    • There will be one or more user names listed. Probably none of them will match the user you think you're logged in as.
    • 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 be the same as the 'Full Name', which should match a user on Windows Home Server.
    This occurs because Windows distinguishes between the user name and the display name. The display name is what's shown on the logon screen. The user name is that actual user that logs in. 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.
    Friday, August 1, 2008 2:58 AM
    Moderator
  • That did it ! Thank you Thank you Thank you.!

    Makes sense now.

    Add step 4 - Logoff/Logon

    Ken, definitely put this on the top of the FAQ... it seems to happen a lot in this forum!

    Thanks again.

    Friday, August 1, 2008 6:32 AM