3
There are two active user accounts on the Windows 7 Professional server, Owner
, and Guest
.
Owner
is an Administrator with a password.Guest
is the default Guest account with no password, but has been added toRemote Desktop Users
.
When attempting to connect to the server via a Windows 7 Professional client, Guest
accepts RD connections fine, however, Owner
throws an error "Unable to connect to Local Security Authority."
I created a new Administrator account, named Remote
, with the same password as Owner
. Remote Desktop worked perfectly. I then deleted Owner
, and renamed Remote
to Owner
.
Now, Remote Desktop gives the same error ("Unable to connect to Local Security Authority") when attempting to log into the new Owner
. However, attempting to log into Remote
(even though it was renamed to Owner
), works.
Completely at a loss here, what is going on? Why won't Owner
work, and why does Remote Desktop still use the old name on the renamed account?
This is the typical *rap Microsoft has us dealing for years. Make it work first. This has been around from the days of XP. By now it's not a bug it's a feature. – unom – 2015-02-03T11:30:56.660
I had the same rdp problem you had, and it was solved by deleting the old renamed account and creating a new clean account. I can not be sure the cause, but maybe someone here can add to the discussion. – Logman – 2012-09-06T00:13:28.340
try the reg fix from the link, probably only way to rule it out – Logman – 2012-09-06T02:44:49.153