If the remote machine does not enforce NLA (Network Level Authentication), it is still possible to start a remote desktop session by disabling NLA on the client (currenlty not possible from the menu on my remote desktop client v.6.3.96000 that came with windows 8.1). This article documents options for disabling or preventing a requirement for Network Level Authentication for Remote Desktop Connections to XenApp 6 servers. How to Enable or Disable Remote Desktop Connections to a Windows 10 PC You can use the Remote Desktop Connection (mstsc.exe) or Microsoft Remote Desktop app to connect to and control your Windows 10 PC from a remote device. Quick note: unless you disable NLA, elect to configure the remote desktop client ignore certificate mismatches or simply use a client that doesn't bother to verify the end-point (or has their own mechanism to do the same), I am not sure you'll easily be able to get around the certificate requirement. Click on Remote Desktop Services, then under Collections click on the name of the session collection name that you want to modify. If you're hard-coding the value to 0, end-users will not be able to connect to systems set with the "Allow connections only from computers running Remote Desktop with Network Level Authentication" option enabled on the remote system. For whatever reason it is requesting a reboot, so I let it reboot before I start my work. Tweak Remote Desktop security settings; Disable NLA using Group Policy Editor; Disable Network Level Authentication using Registry Editor; Turn off NLA using PowerShell …the access is denied when trying to connect with RDP.To avoid this behavior, on the Gateway Server, you will have to do the following: Go to Gpedit.msc, then under Computer Configuration, click on the Administrative Templates folder, on the Windows Components folder and on Remote Desktop Services: I'm guessing the answer is fairly obvious, but does Windows Server 2016 upwards only support RDP NLA from Windows 8 & 10? Disabling RDP Network Level Authentication (NLA) remotely via the registry So I logged into a server that was setup by another administrator using RDP to configure some software. To reduce the amount of initially required server resources, and thereby mitigate against denial of service attacks, network level authentication (NLA) can be used. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.” Before I talk about the workaround and the PowerShell script we used to fix that, let’s investigate in order to understand the problem. I'm just deploying our first Windows Server 2016 instance and I've had to disable RDP NLA to allow Windows 7 machines to RDP to it. ... To disable NLA, ... to open a Properties window. “The remote computer that 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 by using the options on the Remote tab of the System Properties dialog box.” Click on Tasks and select Edit Properties. Under the Security tab un-tick the option Allow connections only from computers running Remote Desktop with Network Level Authentication. To fix The remote computer requires Network Level Authentication issue on Windows 10/8/7, follow these following solutions-. When you allow remote desktop connections to your PC, you can use another device to connect to your PC and have access to all of your apps, files, and network … If you have NLA enabled on a remote server and need to RDP into it, you may find yourself in a situation where you are locked out and cannot disable the security on the remote machine in order to make the connection.