Remote desktop - "The Local Security Authority cannot be contacted"
After I read the answer by DavidRa I went to the Server 2008 R2 gave me the your password has expired and needs to be changed. I changed it and got in. The 2012 box was the one that gave me the "Local...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Additionally to this particular answer, user forgot to mention that the Domain Policy password expiration ask the user to change password. I ask the user to restart the PC, and once the user change the...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
In my case, it was easier to solve than I thought...I reset the user password from the domain controller. Then, in Active Directory I selected the user and opened the user properties window. In the tab...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I just had the same message "The Local Security Authority cannot be contacted" happen in the following scenario. Windows 7 user using Remote Desktop to log in to a newly upgraded Windows Server 2012....
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Hi,I had the same problem and the same resolution!
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Radu,Thanks for this comment which helped me solve my problem. My user was logging onto their pc with their normal credentials and then using different credentials to RDP to a server. This was not an...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had the same problem in my domain home lab, even i restarted the server I wanted to RDP.What i did is to shutdown all my servers, including domain controller.I started the domain controller. I waited...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I created this same error message by renaming an account. I created the account originally just for remote access and immediately did not like the name I picked so I renamed it. I attempted to...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Unjoin, then re-Join the server to the domain.The server even will show "joined to the domain" (if you look in computer/properties), BUT, for some reason, mine was not completely joined. Go figure. I...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
This did it for me after a good few hours of research. Thanks very much!
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I got this error when I was decommishioning some old domain controllers, the server I was trying to connect to had a static IP set with static DNS server entries. Once the last DNS server was powered...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
@Smarcell: You sir, are a savior. Thank you! Can't believe a bug like this passed right under MS's nose.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
It worked for me. You could write {machinename}\{localusername} in user name bracket instead.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
What Language packs do you have installed?An authentication error has occurred. The Local Security Authority cannot be contactedPeteRegards Pete Long http://www.petenetlive.com
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
try find the solution herehttp://support.microsoft.com/kb/2493594
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I fixed it with running the command "ipconfig /flushdns" in the CMD.exe on the server.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had this same problem. 2 accounts. Both could log in locally only one could RDP. The one that could not was station restricted. Turned off NLA and then it could log right in.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Hi Guys,I got the same issue when I do a remote desktop to Server 2012 Hyper-V Core, I reset the password - It didn't work for me.I rebooted after reset the password - It didn't workI disabled the...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had this problem on a Windows 8 RTM installation in a domain environment. A domain user was able to log on locally but not through Remote desktop. Another domain user was able to logon both locally...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Make sure you can ping the FQDN. I had this issue and was unable to ping DevDomainSrv.Dev.Local, but I could ping DevDomainSrv. When I took a look at the network adapter properties, the DNS setting...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Well, the solution for my issue was to reset the user account password eventhough it is not expiring. This seems to be the work around so far./* Server Support Specialist */
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
That is a workaround, but NLA is normally fine until this problem pops up.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
We just needed to set "Allow connections from computers running any version of Remote Desktop (less secure)"... instead of the NLA option.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Exactly. Thanks a bunch! In my case I used Core Configurator 2.0 on Server Core 2008 R2. I did not intend to change any DNS settings, maybe it's a bug in Core Configurator. Anyways: if you try to log...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
For what it is worth I was having this issue with a Windows 7 SP1 x64 machine RDPing to a Window Server 2008 R2 SP1 Datacentre. I could logon locally, but not with a domain account.The domain account...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Here is another solution, looks like this issue is caused by different scenarios, in my case I was still able to logon with my Domain Admin account to a locked down machine(with very tight Domain...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I would have this issue when trying to RDP into a DC after it was rebooted (not very often). I could log into them locally with no errors and would have to do so to "nudge" the server back into letting...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
This one works great. I disabled the check mark on the profile asking for password expires; etc.. and works great. Then I asked the user to come to my desk and changed the password! :)
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I've run in this problem after inplace upgrade of W2k3 into w2k8What I've found is that when You set "Log On To" to the user account and add a few computers remember to add the one that user is running...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Assuming you have RDP setup correctly on the client and server:My solution was to UNCHECK the 'Allow connections only from computers....' in System properties , Remote tab.Working now.Less secure?...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had the same error on my Azure virtual machine and a local virtual machine. I resolved this error by following the under given...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
This worked for me too. My original issue was caused by removal of one DC and addition of another, while having the new one seize the Schema Master and Domain Naming Master fsmo roles.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
HiIn my humble opinion, I think the the issue comes from the local accountsI think that the local account is set to "User must change password at next logon"Hope it will help some folks !
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I have the same issue, So I unchecked the "user must change password at next logon" option and It worked for me.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I know this is a really old thread. But I *finally* figured this out with what for me is the DEFINITIVE solution. I get the "local security authority could not be contacted" error too, when attempting...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had the same problem which was easily mitigated by disabling NLA for the remote connection (which is a trivial workaround) but the true reason for this error message was that the server could not...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I had this issue with a 2008 R2 Server after it rebooted after updates. I remotely logged on using the local credentials, and found that the nework adapter was saying private network instead of domain....
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
i had the same issue pop up, though mine is on a domain. The problem was the comcast router that was recently replaced, which has no ability to turn off DHCP for ipv6, handing out incorrect IPV6...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I starting having this issue after I updated to Windows CU 1703 from Windows 10 Anniversary edition. The PC is NOT part of a domain. I can't figure it out. ------ Sean J Vreeland Seattle, WA
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
For me I couldn't even do a reset of the password. I had to check the box that says "Password Never Expires".If it is checked my user can loginIf it is not checked .... An authentication error has...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
It has literally taken me days to figure out my specific issue for my specific setup. First the setup.Runnint a Server 2012 Standard domain controller with Group Policy and Hyper-V.In AD DS some users...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Hi All Osman's steps solved this issue but I will like to make it very simple.CRight click on Computer/ This Computer, Select PropertiesOn the Top Left, Select Remote SettingsThis will Take you to...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Hi all,For me, it was on a tiny network that had two domain controllers, but one crashed a while ago, and I had no plans to replace it. I hadn't removed it from Active Directory, though. I was...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
if you renew the IP on the remote machine, it should work : - open command prompt- type "ipconfig /release"- type "ipconfig /renew"
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Just Uninstall KB4480968(patch date year 2019) Windows security patch.after uninstall patch just restart your server.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
I dont have that patch and have the same issue.
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Check that the account does not have an expired password, and that the account itself is not expired. In my case, the account password had expired, causing this error. As soon as I changed the...
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
Same fix for an old Windows Server 2008 x86 server.I also found that if I added the remote PC's hostname to the list it worked.Don
View ArticleRemote desktop - "The Local Security Authority cannot be contacted"
In Local Security Policy/Local Policies/User Rights Assignment, remove Guest from "Deny access to this computer from the network". As mentioned by another person on this thread, you might also need to...
View Article