Skip to main content

How to Fix ‘The Local Security Authority Cannot be Contacted’ Error on Windows

This error appears when users try to login to other computers via a remote desktop connection. The problem prevents them from connecting and it displays the “The Local Security Authority Cannot be Contacted” error message. The problem often appears after an update has been installed on either the client or the host PC and it causes plenty of problems on many different versions of Windows.
The Local Security Authority Cannot be Contacted
There have been many unofficial fixes for the problem which were created by the users who had the same unfortunate experience. We have gathered the working methods in this article so make sure you follow it in order to resolve the problem.

What Causes “The Local Security Authority Cannot be Contacted” Error on Windows?

Pinpointing the correct cause for the problem is one of the most important steps when it comes to resolving one. That is why we have created a list of possible causes for the problem so make sure you check it out below:
  • DNS addresses may be wrongly configured – If this is indeed the case, try using the DNS addresses provided by Google or OpenDNS
  • Remote Desktop connections may be disabled by default on either the host or the client PC – Make sure you turn the option on to connect properly without errors.
  • IP and DNS address conflicts – Running a certain command may help you resolve the problem

Solution 1: Change Your DNS Address

The problem is often caused by a faulty DNS setup which is simply not accepted by the host or its service. The problem can be resolved easily by changing your default DNS settings to use the ones provided by OpenDNS or Google. This can be done easily in Control Panel so make sure you follow the steps below carefully.
  1. Use the Windows + R key combo which should immediately open the Run dialog box where you should type ‘ncpa.cpl’ in the bar and click OK in order to open the Internet Connection Settings item in Control Panel.
  2. The same process can also be done by manually opening Control Panel. Switch the View by setting at the top right section of the window to Category and click on Network and Internet at the top. Click the Network and Sharing Center button in order to open it. Try to locate the Change adapter settings button at the left menu and click on it.
Change adapter settings
  1. Now that the Internet Connection window is open using any method above, double-click on your active network adapter and click on the Properties button below if you have admin permissions.
  2. Locate the Internet Protocol Version 4 (TCP/IPv4) item on the list. Click on it in order to select it and click the Properties button below.
Internet Protocol Version 4 – Properties
  1. Stay in the General tab and switch the radio button in the Properties window to “Use the following DNS server addresses” if it was set to something else.
  2. Set Preferred DNS server to be 8.8.8.8 and the Alternate DNS server to be 8.8.4.4
Setting the DNS address to Google DNS or OpenDNS
  1. Keep the “Validate settings upon exit” option checked and click OK in order to apply the changes immediately. Check to see if the same problem still appears!

Solution 2: Enable Remote Connections in Group Policy Editor

Sometimes the Group Policy on the client computer is preventing the remote Desktop connection completely. This can be changed quite easily in Group Policy Editor if you are running any version of Windows besides Windows Home. Follow the steps below in order to enable remote connections in Group Policy Editor.
  1. Use the Windows Key + R key combination (tap the keys simultaneously) to open the Run dialog box. Enter “gpedit.msc” in the Run dialog box, and press the OK button in order to open the Local Group Policy Editortool. On Windows 10, you can try simply type Group Policy Editor in the Start menu and click the top result.
Running Group Policy Editor
  1. On the left navigation pane of Local Group Policy Editor, under Computer Configuration, double click on Administrative Templates, and navigate to the Windows Components>> Remote Desktop Services >> Remote Desktop Session Host >> Connections.
    Allow users to connect remotely by using Remote Desktop Services
  2. Select the Connections folder by left-clicking on it and check out its right side section.
  3. Double click on the “Allow users to connect remotely by using Remote Desktop Services” policy and check the radio button next to the “Enabled” option.
Enabling the policy
  1. Apply the changes you have made before exiting. The changes won’t be applied until you restart.
  2. Finally, reboot the computer to save the changes and check to see if you are still being targeted with the error.

Solution 3: Allow the Connection inside System Properties

The most common cause for the problem is the fact that remote access is, in one way or another, blocked on either the host or the client PC. This time, the problem may be with the host PC which may not be accepting connections from other PCs or the ones with another version of Remote Desktop running. Follow the steps below in order to fix this.
  1. Right-click either on My Computer/This PC depending on the version of Windows you have installed on your computer and choose the Properties
  2. After that, locate the Change settings button at the left side of the Properties window, under Computer name, domain, and workgroup settings, and click on it.
Change settings button in This PC >> Properties
  1. In the Remote tab of System properties, check under Remote Desktop and click the radio button next to Allow remote connections to this computer. Also, uncheck the box next to the Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).
Allow remote connections to this computer
  1. Apply the changes you have made and check to see if the problem still appears.

Solution 4: Run a Helpful Command on the Host

This method is quite popular for its simplicity and plenty of people use it in order to fix most things related to connectivity issues. The funny thing is that it works and users have commented saying that this is the only step it took to resolve the problem. Try it out now!
  1. Search for “Command Prompt” by typing it right in the Start menu or by pressing the search button right next to it. Right-click the first entry which will pop up as a search result and select the “Run as administrator” option from the context menu.
  2. Additionally, you can also use the Windows Logo Key + R key combination in order to bring up the Run dialog box. Type in “cmd” in the dialog box which appears and use the Ctrl + Shift + Enter key combinationfor administrative Command Prompt.
Running Command Prompt
  1. Type in the following command in the window and make sure you press Enter after typing it out. Wait for the “Operation completed successfully” message or something similar to know that the method worked.
ipconfig/flushdns
  1. Try to reset the connection and check to see if the error still appears.

Comments

Popular posts from this blog

Fix: System Found Unauthorized Changes on the Firmware, Operating System or UEFI Drivers

Several users are struggling with the  System found unauthorized changes on the firmware error  at every startup or when trying to take their computer out of hibernation mode. Most affected users report that the issue started occurring after they installed some pending Windows updates. The issue is mostly encountered on Windows 7. The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [OK] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. What is causing the System found unauthorized changes on the firmware error We investigated this particular issue by looking at various user reports. This error will occur whenever your system is checking the firmware one some computer hardware parts as part of a new security feature. To be precise, the error is occurring because not all Windows versions will support this new security feature. As it turns out, there are sev...

Fix: The Following Error Occurred Attempting to Join the Domain

Several users are getting the ‘ following error occurred attempting to join the domain ‘ error when trying to connect a computer to a home or work domain. Most of the time, the error is accompanied by an explanation message telling the user that it has exceeded the maximum number of computer accounts. The issue is not restricted to computers that connect to a domain for the first time, as it’s often reported to occur with PCs and laptops previously connected to the same domain. The following error occurred attempting to join the domain. Your computer could not be joined to the domain. What is causing the ‘following error occurred attempting to join the domain’ error? We investigated this particular error by looking at various user reports and the troubleshooting guides that they themselves followed to get the issue resolved. Based on what we were able to gather, there are several different scenarios that might trigger this particular error message: SMB1 support is di...

How to Fix Startup Repair Loop on Windows 7

Getting a  boot loop  which doesn’t let you go past the  Startup Repair  in Windows 7 is something that a lot of users have experienced, and it is most likely due to corrupt registry entries. It might be your mistake if you have messed around in the registry and changed a key you shouldn’t have, but it can also happen by itself, as Windows isn’t really immune to that kind of problems. No matter whether it is your fault or not, you will not be able to boot up Windows, as it will be stuck rebooting itself and won’t make it past the  Startup Repair  screen no matter what. However, there is a solution that begins at the Startup Repair screen, and uses the command prompt to fix the problem by backing up your files, and refreshing Windows, so follow the steps below to see how you can get out of the boot loop. Backup your old files and refresh your Windows In order to start the system in start-up repair, you will need either the windows installation ...