Fix Local Security Authority Cannot Be Contacted Error

This error typically appears when you try to access a shared folder, printer, or remote computer on a Windows network, and it means your PC can’t reach the Local Security Authority (LSA) service that handles authentication. The fix usually involves checking the LSA service, network settings, or Group Policy. Below are the most effective steps to resolve it, starting with the simplest.

What You’ll Need

• Administrator access to your Windows PC (to change services and policies).
• The name or IP address of the computer you’re trying to connect to.
• A few minutes and patience—some steps require a restart.

Step-by-Step

1. Restart your PC. This clears temporary glitches in the LSA service. If the error is gone after reboot, you’re done. If not, continue.
2. Check if the LSA service is running. Press Win + R, type services.msc, and press Enter. Scroll to Security Accounts Manager and Local Security Authority (or Credential Manager on older Windows). Double-click each, ensure the Startup type is Automatic and the service status is Running. If not, click Start, then OK. Restart your PC and try again.
3. Verify network discovery and file sharing are on. Open Control Panel → Network and Sharing Center → Advanced sharing settings. Make sure Turn on network discovery and Turn on file and printer sharing are selected for your current network profile (Private or Public). Save changes.
4. Check the Windows Firewall. Sometimes the firewall blocks LSA-related ports. Go to Control Panel → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall. Ensure File and Printer Sharing is checked for both Private and Public networks. If it’s not, click Change settings, check it, and click OK.
5. Reset the Local Security Authority cache. Open Command Prompt as Administrator (search cmd, right-click, Run as administrator). Type gpupdate /force and press Enter. Wait for it to complete, then restart.
6. Modify Group Policy (if the above fails). Press Win + R, type gpedit.msc (Pro/Enterprise only), and navigate to Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options. Find Network security: LAN Manager authentication level. Set it to Send LM & NTLM responses (or lower). Click OK and restart. Note: This lowers security, so only do it if you trust the network.
7. Check the target computer’s IP. If you’re using a hostname, try the IP address instead. Open Command Prompt and type ping to see if it resolves. If not, use the IP from ipconfig on the target machine.
8. Ensure both computers are in the same workgroup. Right-click This PC → Properties → Advanced system settings → Computer Name tab. Note the Workgroup name. Both machines must have the same workgroup (e.g., WORKGROUP). If not, click Change and set it, then restart.
9. Disable IPv6 (temporary test). In Network Connections, right-click your adapter → Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and restart. If the error disappears, re-enable IPv6 and consider updating your network driver.
10. Run the Windows Network Troubleshooter. Go to Settings → Update & Security → Troubleshoot → Additional troubleshooters → Network Adapter and Shared Folders. Run both and follow the prompts.

Common Mistakes

• Changing Group Policy without restarting: The policy change only takes effect after a reboot or gpupdate /force.
• Disabling the firewall entirely: This can open your PC to threats. Only adjust specific rules.
• Using the wrong network profile: If you’re on a Public network, many sharing features are blocked by default. Switch to Private if it’s a trusted network.
• Typing the computer name incorrectly: A simple typo causes this error. Double-check the name or use the IP.
• Ignoring the target PC’s settings: The error can be on the remote computer, not yours. Apply the same steps to the machine you’re connecting to.

Tips

• Use IP addresses for quick tests: If hostname resolution is the issue, IP bypasses DNS.
• Keep Windows updated: Many LSA-related bugs are fixed in cumulative updates. Check for updates in Settings.
• Create a restore point before making Group Policy changes: This lets you revert if something goes wrong.
• Check the date/time on both machines: Kerberos authentication can fail if the clocks are off by more than a few minutes. Sync both to internet time.
• Use the built-in net use command: Open Command Prompt and type net use \\computer\share to see a more specific error message that can guide you.

Troubleshooting

If the error persists after trying all steps:

• Check the Event Viewer: Press Win + R, type eventvwr.msc, and look under Windows Logs → System for errors related to LSA or Security. The error code may point to a specific cause.
• Try connecting from a different user account: Create a new local user, add it to the Administrators group, and try accessing the share. This isolates a profile corruption.
• Check if the target computer has a password-protected share: If the remote machine requires a password, ensure you’re entering the correct credentials. Try using the format COMPUTERNAME\Username.
• Reset the network stack: Run these commands in an elevated Command Prompt: netsh winsock reset, netsh int ip reset, then restart.
• Disable SMB1 (if enabled): SMB1 is outdated and insecure. Open PowerShell as Admin and run Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol if it’s enabled. This can sometimes resolve authentication conflicts.
• If all else fails, consider a system file check: Run sfc /scannow in an elevated Command Prompt to repair corrupted system files.

Frequently Asked Questions

Q: What exactly is the Local Security Authority?
A: It’s a Windows subsystem that handles security policies and user authentication on your PC. When it’s unreachable, your computer can’t validate credentials for network connections.

Q: Can this error happen on Windows 10 and 11?
A: Yes, it occurs on both, as well as older versions like Windows 8. The steps are similar, though some menu names differ slightly.

Q: Is it safe to change the LAN Manager authentication level?
A: Lowering it reduces security because it allows older, less secure protocols. Only do this on trusted networks and revert it after testing.

Q: Why does this error occur when I try to access a shared printer?
A: The same LSA service is used for printer sharing authentication. The fixes above apply to any network resource that requires authentication.

Q: Do I need to be an administrator to fix this?
A: Yes, most steps require admin rights, especially changing services, Group Policy, and firewall settings.

Q: Will reinstalling Windows fix this?
A: It’s a last resort. Try all the steps, including system file checks, before a reinstall. Often the issue is a misconfiguration, not a corrupted OS.

Related

• Siri Not Working on iPhone 6s? Fixes That Work
• Fix Microsoft Store Error 0x80131500
• Snapchat Error Code SS07: Fixes That Work