Mets Minor League Blog

Music theory, instruments and musicians

Mets Minor League Blog

Music theory, instruments and musicians

Fix Remote Requires Network Level Authentication in Windows

By metsPosted on Posted in Sport Gear

Fix Remote Requires Network Level Authentication in Windows

Encountering the message that the remote computer requires network level authentication (NLA) can prevent you from establishing a remote desktop connection. This issue often arises due to misconfigured settings on either the client or the host machine, outdated system files, or security policies that block NLA. Fixing this allows seamless remote access, essential for remote work, troubleshooting, or managing servers remotely. Before starting, ensure you have administrator access on both computers and that both are connected to the network properly.

What You’ll Need

  • Administrator privileges on both the local and remote computers
  • Remote Desktop enabled on the target (remote) computer
  • Network connectivity between the two computers
  • Updated Windows operating system on both machines
  • Optional: Access to Group Policy Editor (for advanced configurations)

Step-by-Step

  1. Verify Remote Desktop is Enabled on the Remote Computer
    Ensure that the remote computer has Remote Desktop enabled. To do this:

    • Open Settings by pressing Windows key + I.
    • Navigate to System > Remote Desktop.
    • Toggle Enable Remote Desktop to On.
    • Note the PC name listed under this section, as you’ll need it to connect.
  2. Check Network Level Authentication Settings on the Remote Computer
    Make sure the remote computer is configured to allow NLA:

    • Open the Start menu, type System, and select System.
    • Click on Remote settings on the left panel.
    • In the Remote Desktop section, ensure that Allow remote connections to this computer is selected.
    • Check the box that says Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure).
    • Click Apply and OK.
  3. Update Windows and Network Drivers
    Outdated Windows files or network drivers can cause NLA issues:

    • Open Settings > Update & Security > Windows Update.
    • Click Check for updates and install any available updates.
    • Update network drivers via Device Manager: Right-click Start, select Device Manager, expand Network adapters, right-click your network device, and choose Update driver.
  4. Configure Group Policy Settings (for Windows Pro and Enterprise)
    If you’re on a Windows Pro or Enterprise edition, verify Group Policy settings:

    • Press Windows key + R, type gpedit.msc, and press Enter.
    • Navigate to Computer Configuration > Administrative Templates > System > Credentials Delegation.
    • Double-click Allow delegating saved credentials with NTLM-only server authentication.
    • Set it to Enabled and click Show to add the value: TERMSRV/*.
    • Repeat for Allow delegating saved credentials.
    • Close the editor and restart the remote computer.
  5. Adjust Registry Settings (if necessary)
    Sometimes, registry tweaks are required:

    • Open Registry Editor by pressing Windows key + R, typing regedit, and hitting Enter.
    • Navigate to HKEY_LOCAL_MACHINE\\SYSTEM\CurrentControlSet\Control\Lsa.
    • Find the value Security Packages. Double-click and ensure it includes kerberos,msv1_0,schannel,wdigest,msnsssp,spnego,credssp.
    • If credssp is missing, add it.
    • Close Registry Editor and restart the remote computer.
  6. Test the Connection
    From your local machine, open Remote Desktop Connection:

    • Press Windows key + R, type mstsc, and press Enter.
    • Enter the PC name or IP address of the remote machine.
    • Click Connect.
    • If prompted for credentials, input the correct username and password.

Common Mistakes

  • Not enabling Remote Desktop on the remote machine.
  • Forgetting to check the box that allows only NLA connections.
  • Using outdated Windows versions that do not support NLA properly.
  • Incorrectly configuring Group Policy or registry settings.
  • Network issues blocking the connection, such as firewalls or VPN restrictions.
  • Using incorrect credentials or username syntax.

Tips

  • Always keep Windows updated to avoid compatibility issues.
  • Ensure firewalls on both machines are configured to allow Remote Desktop (port 3389).
  • If connecting over the internet, use a VPN or port forwarding securely.
  • Test network connectivity with ping or tracert commands.
  • Use the correct PC name or IP address to avoid DNS issues.
  • Consider disabling NLA temporarily to troubleshoot, then re-enable it once fixed.

Troubleshooting

If the steps above do not resolve the issue, consider the following troubleshooting tips:

  • Check Firewall Settings: Ensure Windows Firewall or third-party firewalls allow Remote Desktop connections on port 3389. You can verify this in Control Panel > Windows Defender Firewall > Allowed apps.
  • Test Network Connection: Use the command prompt to ping the remote machine or use telnet to test port 3389 connectivity: 
    telnet remote_ip 3389

    If the connection fails, investigate network issues or firewall blocking.

  • Disable NLA Temporarily: On the remote computer, temporarily disable NLA to see if you can connect without it. If successful, the issue is with NLA configuration. Remember to re-enable security features afterwards.
  • Check Event Viewer: On the remote machine, open Event Viewer (Windows key + R, type eventvwr.msc) and navigate to Windows Logs > Security or System for relevant errors.
  • Reboot Both Machines: Sometimes, a simple restart can resolve temporary glitches.
  • Verify User Permissions: Ensure your user account has permission to connect remotely. Check in System Properties > Remote > Select Users.

Frequently Asked Questions

1. Why do I get the error about network level authentication when trying to connect?

This error occurs because the client is trying to connect with NLA enabled, but the remote machine is not configured to support it, or there’s a misconfiguration in security settings.

2. Can I disable NLA to fix the connection issue?

Yes, you can temporarily disable NLA on the remote machine via System Properties. However, this reduces security, so re-enable it after troubleshooting.

3. Is it safe to disable NLA permanently?

Disabling NLA makes your system more vulnerable to unauthorized access. It is recommended only as a temporary troubleshooting step and re-enabled once the issue is resolved.

4. Will updating Windows fix the NLA problem?

Updating Windows often resolves compatibility issues and security bugs that can interfere with NLA, so it’s a good first step in troubleshooting.

5. How do firewalls affect NLA and remote connections?

Firewalls must allow inbound traffic on port 3389 for Remote Desktop. Blocking this port prevents remote connections, including those requiring NLA.

6. What should I do if I still can’t connect after following all steps?

Consult your network administrator or IT support, as there may be deeper network policies or security settings blocking the connection. Also, verify that the remote machine is powered on and connected properly.

Related

Fix Remote Requires Network Level Authentication in Windows
Scroll to top