Remote computer requires network-level authentication

Users are reporting an error listed below on systems connected to the domain when they try to access computer systems remotely. This occurs even when network level authentication (o NLA) is enabled on the computer. There are simple solutions to solve this problem. You can disable the option directly using the properties or you can make some registry changes and try to reboot the system.

The remote computer you are trying to connect to requires network level authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA using the options on the remote tab of the System Properties dialog.

Or this can also happen:

The remote computer requires network-level authentication, that your computer does not support. To get help, contact your system administrator or technical support.

Note: Before following these solutions, it is essential that you backup your data and make a copy of your registry beforehand. Make sure there are no tasks in progress on both computers before continuing.

Solution 1: disable NLA using Properties

Network-level authentication is good. Provides additional security and helps you, as network administrator, to control who can log into which system simply by checking a box. If you choose this, make sure your RDP client has been updated and authenticated domain is the target. You should also be able to see a domain controller.

We will go through the Remote Desktop setup path and simplify things at first. If this doesn't work, we have also covered other solutions after this.

1. Press Windows + R, type »sysdm.cpl» and press Enter. You will be in the properties of the system.

2. Click the remote tab and uncheck »Allow connections only from computers running Remote Desktop with network-level authentication (recommended)«.

1. Press Apply to save changes and exit. Now try logging into the remote computer again and see if the problem is resolved.

Solution 2: disable NLA using Registry

This method also works if you can't run the first one for some reason. However, note that this will require you to restart your computer completely and may mean downtime if you have a production server running. Make sure to save all your work and confirm if there is still anything left in the staging environment.

1. Press Windows + R, scribe “regedit” in the dialog and press Enter to launch the registry editor.

2. Once in the registry editor, click File> Connect network registry. Enter the details of the remote computer and try to connect.

1. Once connected, navigate to the following file path:

HKLM> SYSTEM> CurrentControlSet> Control> Terminal Server> WinStations> RDP-Tcp

1. Now change the following values ​​to 0.

Security layer
User authentication

1. Now navigate to PowerShell and run the command

subtract-computer

Solution 3: disable use of PowerShell

One of my favorite methods to disable NLA without going into much detail is to disable it using the PowerShell command remotely. PowerShell allows you to access the remote computer and then point to the machine, we can run the commands to disable the NLA.

1. Launch PowerShell on your computer by pressing Windows + S, scribe “powershell” in the dialog, right click on the result and select “Execute as an administrator”.

2. Once in PowerShell, run the following command:

$TargetMachine = "Target machine name"
(Get-WmiObject -clase "Win32_TSGeneralSetting" -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filtro "TerminalName=$0027RDP-tcp$0027").SetUserAuthenticationRequired(0)

Here, the “Target machine name” is the name of the machine you are pointing to.

In the example above, the name of the server is “server member”.

Solution 4: use group policy editor

Another way to disable NLA is through the group policy editor. This is useful if you are deactivating the blanket. Please note that the Group Policy Editor is a powerful tool and changing settings that you have no idea about can render your computer unusable. Make sure to backup all settings before proceeding.

1. Press Windows + R, type »gpedit. msc »in the dialog box and hit Enter.

2. Once in the group policy editor, navigate to the next route:

Equipment setup> Administrative Templates> Windows Components> Remote desktop services> Remote Desktop Session Host> Safety

1. Now look for $ 0027 Requires user authentication for remote connections using Network Level Authentication $ 0027 and set it as disabled.

1. After this step, check if the error is resolved.

Note: If even after all these steps you cannot connect, you can try to remove the machine from your domain and then read it. This will reset all the settings and make it fine for you.