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. Mar 17, 2012  Select Require user authentication for remote connections by using Network Level Authentication and double click on it. On the properties screen select Enable and click on OK. Now lets configure the client settings to make sure that we always select to warn in the case the host certificate con not be authenticated. 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.

• Enable Nla For Rdp
• Disable Nla Azure

Enable Nla For Rdp

Hi – I have a funny scenario RDP’ing from a AAD joined Win10 pro machine to a non-AAD RDS server (AD joined, and hosted in Azure, but joined to a standard ‘on-premises’ domain). AD is synced using AD connect from ‘on-premises’ to Azure. Win 10 joined to AAD by user using OOBE (fantastically slick!)When opening MSTSC the default username is always ADNETBIOSUPN and there seems to be nothing I can do to change this. Creating custom RDP file and saving creds works for one connection, then all subsequent connections revert to ADNETBIOSUPN. The RDS server (and ‘on-premises’ DC it auth’s to) won’t auth the user like that. Works fine with just UPN or ADNETBIOSSAMaccountname.Have you come across this scenario? Idea net setter e1732 unlock software by nirav.

Disable Nla Azure

Any suggestions?Thanks.