Share via

RDP The Local Security Authority Cannot be contacted Windows 11 web account

Anonymous
2024-03-22T16:20:13+00:00

Error:

[Window Title]

Remote Desktop Connection

[Content]

An authentication error has occurred.

The Local Security Authority cannot be contacted

Remote computer: *****************

This could be due to an expired password.

Please update your password if it has expired.

For assistance, contact your administrator or technical support.

Error code: 0x0

Extended error code: 0x0

Timestamp (UTC): 03/22/24 03:24:19 PM

Activity ID: f1fd0473-de2d-4a15-a8a4-1d2cfc160400

What I have tried:

I have a HP g4 work station running windows 11 pro logged into my work. I can rdp to it from two separate windows 10 pro computers with no issues that are also logged in with my work account.

I upgraded my main personal Asus work station to windows 11 pro logged in with my personal Microsoft account using mstsc I get the error " local security authority cannot be contacted"

I tried installing the remote desktop store client which can connect to a local account, but I see no way to have it use the Microsoft authenticator required by my work.

I have tried multiple DNS servers external and internal.

I have tried disabling udp connections in rdp

I have tried disabling nla

I have verified windows firewall has exceptions, and tested with disabled

Also applied suggested gpedit settings to enable rdp

I went through the security admin and enabled everything.

My best guess here is my workstation can't connect to aria to authenticate? Or if I can get the store client to use MFA then maybe that will work.

I also cannot enable Lsa on the workstation due to the hardware limitation? But this is an asus b550 with and58003xd with vt enabled. The Microsoft documentation says I don't need it though.

Any ideas? I have been scoring bing and google all day with no luck.

System Info:

Processor AMD Ryzen 7 5800X3D 8-Core Processor 3.60 GHz

Installed RAM 32.0 GB (31.9 GB usable)

Device ID BD9A00C4-6F17-4C9C-B6F9-B4D1B15583DF

Product ID 00330-81477-44260-AA256

System type 64-bit operating system, x64-based processor

Pen and touch No pen or touch input is available for this display

Edition Windows 11 Pro

Version 24H2

Installed on ‎3/‎21/‎2024

OS build 26085.1

Experience Windows Feature Experience Pack 1000.26100.1.0

Windows for home | Windows 11 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

18 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-25T15:12:35+00:00

    Figured this out, you cannot have a PIN enabled and connect via RDP or you get this stupid error.

    @Microsoft fix your error description or enable PIN pass through.

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-03-30T14:19:40+00:00

    Sorry this did not fix the issue. I have tried every suggestion listed in this thread.

    I also just read M$ is depreciating the RDP client... so my work around may eventually break.

    Come on Microsoft fix the LSA pass through for required pins!

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-02-20T17:53:30+00:00

    I can see this error at the same time in the event log Crypto-NCrypt "0x40290423"

    "The requested salt size for signing with RSAPSS does not match what the TPM uses."

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-03-25T22:32:39+00:00

    I'm having the same issue, but it seems like it suddenly started to occur today. Connecting worked fine on Friday, but sometime over the weekend it is a problem now.

    If I connect via the username AzureAD<upn> then it works, although it's just password auth. Seems like some update broke this and it doesn't make sense. Another device here is configured with a PIN and it works totally fine.

    Windows 11 refuses to allow me to disable a PIN to test this theory, though.

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-03-26T15:28:15+00:00

    Funny you posted my issue came back as well, regardless of pin is disabled or not.

    My assumption was security changed something maybe it was a patch.

    I wish Microsoft would respond...

    0 comments No comments