Remote desktop without a password

109

I have an HTPC with a user that has no password and autologin.

I want to be able to connect to it via Remote Desktop without a password, so I can login with the original user. (I don't want to add another user just for the mstsc)

Is there a way of doing that?

The OS is Windows 7, 32bit.

Am.

Posted 2010-02-10T01:31:22.923

Reputation: 1 546

2just beware that this would be a very bad security decision and consider firewalling it or at least do not forward the port out... – bubu – 2010-12-14T15:53:51.447

2This is not a good idea. – Jonathan Rioux – 2012-06-21T22:50:42.977

Another solution: Teamviewer. Rather than running without a password it uses a stored password. – Loren Pechtel – 2013-12-22T20:05:30.627

Answers

141

Yes, this is possible.

By default, Windows will not allow the logon over a network with a blank password. There is a KB article that details how to allow blank passwords for network logons.

You can disable blank password restrictions by using a policy. To locate and change this policy:

Click Start, point to Run, type gpedit.msc, and then click OK to start the Group Policy Editor.
Open Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Limit local account use of blank passwords to console logon only.
Double-click Limit local account use of blank passwords to consol logon only.
Click Disabled, and then click OK.
Quit Group Policy Editor.

NOTE: By default, this policy is on (enabled).

Under the cover, in Registry, this is controlled by

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LimitBlankPasswordUse"=dword:00000000

Therefore, alternatively, this can be achieved by directly setting LimitBlankPasswordUse to 0. Setting it to 1 will restore the default behavior.

After you have enabled this, you will be allowed to log on using a blank password.

William Hilsum

Posted 2010-02-10T01:31:22.923

Reputation: 111 572

This is also a possible fix for the 0x80090304 authentication error using RDP. (Same problem, it just depends on whether you're connecting with NLA or without.) – RobinHood70 – 2014-10-16T19:21:25.297

+1; confirmed on windows 8 as well. – Jossef Harush – 2015-12-26T19:26:11.693

I beg to differ. We didn't have this enabled and someone got in via port forwarding and logged into an account with a blank password. – user2924019 – 2018-03-01T10:23:02.140

After reading this, I decided that it is better (and quicker) to add a password ;) – Aram Paronikyan – 2018-09-26T12:31:32.200

6does this require a reboot, or logoff? – BozoJoe – 2011-11-15T01:52:20.253

I also have the same requirement. I am connecting to windows 2003 server machine from windows 7 machine using 'mstsc'. I have disabled the option "Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Accounts: Limit local account use of blank passwords to console logon only". But still it prompting for password. Any suggestions please? Thanks – None – 2011-12-15T10:04:37.947

6This doesn't require a reboot or logoff. Just set the policy/registry entry on the host PC, then try logging on again from a remote computer and it should work. – Lessan Vaezi – 2013-09-12T08:24:53.457

I believe the setting should be DISABLED as the explanation here seems to indicate:

This security setting determines whether local accounts that are not password protected can be used to log on from locations other than the physical computer console. If enabled, local accounts that are not password protected will only be able to log on at the computer's keyboard.

Default: Enabled.

So, by disabling it, you can then log on using no password.

furball zen

Posted 2010-02-10T01:31:22.923

Reputation: 41