locked
Connect to a PC remotely without password? RRS feed

  • Question

  • Is there a way to set up WHS so that when you do a remote connection to your home PC through the web that you don't need a password for that remote PC? I don't use a password on my home networked PC's. It would be a nuisance to have to log on every time at home when booting up.
    Wednesday, July 22, 2009 6:31 PM

Answers

  • I do that, but it says the account doesn't meet the requirements because it needs a password.

    Regarding security, all my critical files are on my WHS anyhow, so if they have access to that, then gaining access to my actual PC means little.

    Open a run box and type gpedit.msc.  Go to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.  Then, on the right hand side, you'll see Accounts: Limit local account use of blank passwords to console logon only and it should be Enabled (which is the default setting).  Disable it (and although I don't think you need to reboot your client, I would advise it anyway).
    • Proposed as answer by kariya21Moderator Wednesday, July 22, 2009 7:40 PM
    • Marked as answer by MarkBx Wednesday, July 22, 2009 8:05 PM
    Wednesday, July 22, 2009 7:39 PM
    Moderator

All replies

  • Ignoring questions of security, you should be able to connect to any PC on your network using any user id on that PC that's authorized to connect remotely. If that user id doesn't have a password, leave the password field blank when you connect through the Remote Access web site and fill in the user id.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, July 22, 2009 6:58 PM
    Moderator
  • I do that, but it says the account doesn't meet the requirements because it needs a password.

    Regarding security, all my critical files are on my WHS anyhow, so if they have access to that, then gaining access to my actual PC means little.
    Wednesday, July 22, 2009 7:01 PM
  • Ignoring questions of security, you should be able to connect to any PC on your network using any user id on that PC that's authorized to connect remotely. If that user id doesn't have a password, leave the password field blank when you connect through the Remote Access web site and fill in the user id.
    I'm not on the WHS team, I just post a lot. :)

    Actually Ken, you need to change the Group Policy in order to allow remote connections with a blank password.
    Wednesday, July 22, 2009 7:38 PM
    Moderator
  • I do that, but it says the account doesn't meet the requirements because it needs a password.

    Regarding security, all my critical files are on my WHS anyhow, so if they have access to that, then gaining access to my actual PC means little.

    Open a run box and type gpedit.msc.  Go to Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.  Then, on the right hand side, you'll see Accounts: Limit local account use of blank passwords to console logon only and it should be Enabled (which is the default setting).  Disable it (and although I don't think you need to reboot your client, I would advise it anyway).
    • Proposed as answer by kariya21Moderator Wednesday, July 22, 2009 7:40 PM
    • Marked as answer by MarkBx Wednesday, July 22, 2009 8:05 PM
    Wednesday, July 22, 2009 7:39 PM
    Moderator
  • Hmm. Yes. I use passwords everywhere. There may be a way to defeat the password requirement for remote desktop; if so it will require a registry hack and is not recommended. So effectively the answer is no, you can't defeat the requirement.

    As for logging on at home, you can configure your home PCs to autologon using a specific user id and password, though that reduces security significantly. You would need to remember the password(s) for remote desktop access, obviously.

    Question, if you have no passwords on your userids at home, how are you managing to configure accounts for Remote Access? That requires a strong password, which can only be changed through an unsupported registry hack.

    I'm not on the WHS team, I just post a lot. :)
    Wednesday, July 22, 2009 7:52 PM
    Moderator
  • Hmm. Yes. I use passwords everywhere. There may be a way to defeat the password requirement for remote desktop; if so it will require a registry hack and is not recommended. So effectively the answer is no, you can't defeat the requirement.

    No hack required, see my other post. :)

    As for logging on at home, you can configure your home PCs to autologon using a specific user id and password, though that reduces security significantly. You would need to remember the password(s) for remote desktop access, obviously.

    Question, if you have no passwords on your userids at home, how are you managing to configure accounts for Remote Access? That requires a strong password, which can only be changed through an unsupported registry hack.
    I'm not on the WHS team, I just post a lot. :)


    I have 2 accounts set up for myself in WHS.  One is for Remote Access (which requires a strong password) and the other for local access (which has no password).
    Wednesday, July 22, 2009 7:58 PM
    Moderator
  • Well, setting the local policy item described by kariya21 on my Vista and XP machines I can remotely connect without need for a password through WHS. Thanks!

     I have strong passwords for user accounts on WHS, but not same account name on my PC's, so I have to input credentials when I connect to WHS for file sharing folders. No hacks that I've used.

    I'm still tinkering, so I may end up implementing passwords for my PC's if it will streamline the process.
    Wednesday, July 22, 2009 8:04 PM
  • Well, setting the local policy item described by kariya21 on my Vista and XP machines I can remotely connect without need for a password through WHS. Thanks!

     I have strong passwords for user accounts on WHS, but not same account name on my PC's, so I have to input credentials when I connect to WHS for file sharing folders.

    Or just create a second user on your server that matches the user accounts on your clients.  No more password prompts. :)

    No hacks that I've used.

    I'm still tinkering, so I may end up implementing passwords for my PC's if it will streamline the process.

    Wednesday, July 22, 2009 8:09 PM
    Moderator
  • ...
    I'm still tinkering, so I may end up implementing passwords for my PC's if it will streamline the process.
    Passwords for users on home PCs will allow a seamless experience when accessing Windows Home Server shares, because you won't be prompted for credentials, or need to save the credentials for your connection.


    I'm not on the WHS team, I just post a lot. :)
    Thursday, July 23, 2009 3:48 PM
    Moderator