I'm having issues logging into Windows servers using Active Directory accounts while connected to a VPN that links our onsite network to Azure AD. Occasionally, I encounter an NLA (Network Level Authentication) error. When I run the command Test-ComputerSecureChannel, it fails, even though other protocols like ping, Kerberos, LDAP, DNS, RPC, and SMB are functioning properly. Can anyone help me identify what's going wrong and how to resolve it?
2 Answers
It sounds like you have a couple of options here. You could either ensure that your system has trusted domain connectivity or you could disable NLA altogether. To disable NLA, just go to the system settings of the server you’re trying to RDP into. Navigate to Remote Desktop settings, head to advanced settings, and uncheck the 'Require NLA' option.
What do you mean by other protocols being "up"? You didn’t mention the exact error message you're encountering, which makes it a bit harder to troubleshoot. Since you’re on a VPN, maybe clarify if you're using Azure AD Domain Services or your own VMs for directory services. When Test-ComputerSecureChannel fails, it doesn't necessarily interact with NLA on the client side, but it’s important to know what error message you’re getting from that test. Going back to basics could help here!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures