Not able to connect with Sql Server

Question

[Window Title] Remote Desktop Connection

 

[Content] 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. You can try connecting to the remote computer using your username and password instead.

 

[^] Hide details  [OK]

 

[Expanded Information] Error code: 0x0 Extended error code: 0x0 Timestamp (UTC): 04/30/26 04:04:11 PM Activity ID: 66a69afb-f22d-49b8-bb10-ddb7511f0100

Answer 1

Refer to https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/cannot-connect-rdp-azure-vm

When you try to connect to the VM by using Remote Desktop Connection, you receive one of the following error messages:

• An authentication error has occurred. The Local Security Authority cannot be contacted.
• The remote computer that you are trying to connect to require 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.
• This computer can't connect to the remote computer. Try connecting again, if the problem continues, contact the owner of the remote computer or your network administrator.

Cause

There are multiple reasons why NLA might block the RDP access to a VM:

• The VM cannot communicate with the domain controller (DC). This problem could prevent an RDP session from accessing a VM by using domain credentials. However, you would still be able to log on by using the Local Administrator credentials. This problem may occur in the following situations:
  • The Active Directory Security Channel between this VM and the DC is broken.
  • The VM has an old copy of the account password and the DC has a newer copy.
  • The DC that this VM is connecting to is unhealthy.
• The encryption level of the VM is higher than the one that's used by the client computer.
• The TLS 1.0, 1.1, or 1.2 (server) protocols are disabled on the VM. The VM was set up to disable logging on by using domain credentials, and the Local Security Authority (LSA) is set up incorrectly.
• The VM was set up to accept only Federal Information Processing Standard (FIPS)-compliant algorithm connections. This is usually done by using Active Directory policy. This is a rare configuration, but FIPS can be enforced for Remote Desktop connections only.

---

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin