RDP Problem invalid password - even though password is ok.

[TheDoc46]

Hi,

I've setup my home network, so that each machine can RDP to each other. All machines are running Win7 64-bit, not that it should matter, but all the machines are on the same homegroup, and all have the same one username, with no password enabled on any.

Anyway cutting a long story short,

Under all the machines, in Remote Settings, I'm allowing connections from computers running any version of Remote Desktop.

Because I dont have the need for protecting my machines with a password, the passwork is left blank on all the machines.

However I can't RDP onto only one of my machines.

I've gone into the GPEDIT.MSC under, Windows settings, Security Settings, Local Policies, Security Options, Accounts: Limit local account use of blank passwords to ENABLED.

However, if I try and RDP to this machine, it tells me invalid password.

If I enable a password on this machine, i can RDP onto it, (i tried that as part of my troubleshooting process) Then i tried removing the password to see if that would clear the problem, and unfortunately the invalid password error came back.

I have all my other machines setup the same way, with no password and it lets me RDP on to all of them without issue, thanks to the GPEDIT.MSC entry, It's just on this one, where it wants the password even though there's none set and the use of blank passwords is allowed.

Can anyone point me to a registry key that I may need to delete ?

I've also run the GPUpdate /force command in hope that, that would help, which it didn't. and of course the enabling and disabling of the GPEDIT.MSC entry, with reboots inbetween.

I'm stuck lol

Anyone able to help please ?

 

[Layback Bear]

Just a though from a non expert. Does each computer have a different name? Computer blue, computer red, ect.

 

[Kaktussoft]

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.

 

[chev65]

I'm surprised that Homegroups works at all with those machines running the same User name.

When ever I used the same User name the machines with the same name didn't even show up on the network.

As to the password problem, Maybe the time/date settings are off.

 

[TheDoc46]

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.

All of which is in my OP. As i said that KB Article has been set to allow blank passwords, and it doesn't work on the problem machine. BUT just on that one machine. Works fine on all the others.

 

[TheDoc46]

I'm surprised that Homegroups works at all with those machines running the same User name.

When ever I used the same User name the machines with the same name didn't even show up on the network.

As to the password problem, Maybe the time/date settings are off.

Username not computer name is fine for homegroups.

time/date settings not the problem as i can add a password to the account and get on. Besides which the time is showing as accurate.

 

[TheDoc46]

I guess a simplier request to my question would be, what else is there to try, when the Limit local account use of blank passwords, is disabled and still not working.

 

[Kaktussoft]

Impossible

 

[TheDoc46]

Impossible

What exactly is impossible? The fact that it doesn't work ? even though the option is enabled?

There's something else at play here, and no-one seems to know what.

 

[UsernameIssues]

....However I can't RDP onto only one of my machines.

I've gone into the GPEDIT.MSC under, Windows settings, Security Settings, Local Policies, Security Options, Accounts: Limit local account use of blank passwords to ENABLED.

However, if I try and RDP to this machine, it tells me invalid password.....

RDP works for me to a W7pro computer without a password if I disable that policy.

Edit: yes - I know that you tried both settings. I was just speaking to the fact that it is obviously possible. Still scratching my head as to what else it could be.

 

[UsernameIssues]

I was looking for a way for you to export the group policy settings from a working computers. That lead me to this: Security Compliance Manager (SCM) but I don't think that you want to install all of the stuff that comes with that tool.

Are there any entries in the various Windows event logs - maybe the security log - that might give us a hint as to why this one computer acts so differently than your other computers?