How to Fix The Remote Computer requires network level authentication

Keep reading to learn How to Fix The Remote Computer requires network level authentication, because here you will find all that you need.

This error message may also appear when you try to connect to a faraway computer using the Distant Desktop Protocol, RDP. In simple words, what this error message is trying to tell you is that the remote computer is configured to accept connections only from devices that are compatible with NLA.

General reasons that may be involved include outdated versions of Windows, faulty RDP configuration, the inability of a user's system or network to authenticate via NLA, and the inability of the remote computer to access the required domain controller to authenticate. 

Let us outline a few of them in this article.

1. Properties to Disable NLA

You can disable NLA in System Properties as a workaround to ensure connectivity. This will allow you to connect to the remote desktop without needing NLA. This bypasses the extra authentication phase, which may be problematic if your device or network doesn't completely support NLA.

Note that disabling NLA also reduces the security of the remote connection in that it does not check for the identity of the user before beginning the session. 

Open Run with Windows + R and type "sysdm.cpl". You will be taken to system properties. 

In the Remote tab, uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).".

Click the Apply button to save changes and then exit. Attempt to reconnect to the remote computer. If that doesn't work, try it again.

2. Disable NLA Using Registry

For that, you need to go into the Windows registry and disable Network Level Authentication. You can configure the system to bypass the necessity to attempt an NLA by changing some of the registry keys, which in turn permits connections when the machine isn't in a position to authenticate with the domain controller. That is quite helpful in scenarios where authentication fails due to older RDP clients or because of network issues.

Hit Windows + R, type in "regedit" within the dialogue box, and press Enter to open up the Windows Registry Editor.  

Open registry editor and click on File > Connect Network Registry. Input details of the remote PC and see if it connects. 

Once connected, navigate to this folder: 

terminal server, windows, RDP-TCP, HKLM:system, current control set, control, terminal server, windows, and terminal services

Put zeroes in the following fields:User Authentication at the SecurityLayer  

Now restart your computer to see if this fixes the problem.  

disable nla via powershell

3. Using PowerShell to Disable NLA

With PowerShell, it is relatively easy and fast to disable NLA in order to get around the problem. You run a couple of commands, such as SetUserAuthenticationRequired(0), which will alter configuration on the system about how authentication of remote desktop connections should be performed. Now, any RDP client, whether supporting NLA or not, is capable of connecting since the requirement has been lifted.

Press Windows + S to open the dialog window, input "powershell", right-click on the result and select "Run as administrator" to open the PowerShell. 

The following is a script you can execute in PowerShell:

$TargetMachine = "Target-Machine-Name. "

(Using the following command : (Get-WmiObject -class "Win32_TSGeneralSetting" -Namespace rootcimv2 erminalservices -ComputerName)

Using the filter "TerminalName='RDP-tcp'"

Select $TargetMachine )

User authentication required.

Here, "Target-Machine-Name" is the name of the machine.

Figure : A server named "member-server"

4. Via Group Policy Editor

We can bypass this NLA issue by making some changes to the authentication mechanisms of Remote Desktop with the help of Group Policy Editor. By disabling the need to have NLA enabled for connections, connections can be accepted without this security check. This helps when the system cannot correctly authenticate because of issues at the network or DNS levels. This little tweak may also let us bypass the most common mistakes caused by NLA and hence allow remote sessions instead.

Press the Windows + R and open the Run dialogue box. In the box, type in gpedit.msc and press Enter.

Apply the following in the Group Policy Editor:

Under Computer Configuration, click Security from the options, then go to Administrative Templates, then Windows Components, Remote Desktop Services, and RDS Host.

Scroll down towards "Require user authentication for remote connections by using Network Level Authentication." Click on that, and click the toggle to move it to the disabled state.  

Assuredly, the problem is now fixed.

Note that if this does not work after trying the above, you may want to delete the machine from your domain and then add it again. This will reset all settings to factory default in order to get it working for you.

That is all you need to know concerning How to Fix The Remote Computer requires network level authentication, so we hope that we have been very helpful.