Windows Remote Desktop fails after disconnecting and reconnecting a few times Error Code 0x3 Extended 0x0

Question

I have a RDP connection set up for one of my windows machines remotely that doesn't seem to work anymore after I connect a couple of times. Initially restarting the machine fixed the connection but now it is instantly failing after I enter my credentials:

[Window Title]
Remote Desktop Connection

[Content]
Your Remote Desktop Services session has ended, possibly for one of the following reasons:

The administrator has ended the session.
An error occurred while the connection was being established.
A network problem occurred.

For help solving the problem, see "Remote Desktop" in Help and Support.

[^] Hide details [OK]

[Expanded Information]
Error code: 0x3
Extended error code: 0x0
Timestamp (UTC): 01/07/25 09:03:14 PM

Something to note is that the timestamp is wrong, it is five hours ahead of what it should be.

Thanks!

***Move from Windows / Windows 11 / Apps / Windows apps ***

Answer 1

Hello，

Your error message and code are regular error messages, to troubleshoot this issue, ·we'll need to gather more information and perform some diagnostic steps.

1. What are the OS versions of the client and server?
2. Is this problem occurring for all clients and all accounts remotely connected to this Windows computer?
3. Can the client ping the IP address of the destination server be pinged?
4. Is it normal to log in to the target server in the console?
5. Make sure that both the Windows system and the relevant drivers are up to date.
6. Open the Event Viewer and navigate to: Applications and Services Logs>Microsoft>Windows>RemoteDesktopServices-RdpCoreTS and TerminalServices-LocalSessionManager, check whether the error message is reported at the point in time when the problem occurred.
7. Open the Group Policy Editor (gpedit.msc) on the target server, navigate to: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security，disable“Require user authentication for remote connections by using Network Level Authentication”, then enable“Require use of specific layer for remote(RDP) connections”，And change the security layer to the RDP security layer.

Open cmd with administrator privileges, run gpupdate /force to make the modification take effect, restart the server, and then try to connect remotely to see if the problem can be reproduced.

I hope this information helps.

Best regards,

Jingjing Wu

Answer 2

1. both the client and the server are running Windows 11 Pro Edition
2. I only have my Microsoft account allowed in the policy editor and I've tried on two separate clients with the same error.
3. Yes
4. No, I usually use the GUI provided by the Remote Desktop Connection app.
5. Okay I will ensure they are up-to-date.

I don't have access to the remote computer currently but in a couple of hours I can try your recommended steps.

Thank you so much!

Answer 3

6. I see a bunch of warnings in RemoteDesktopServices-RdpCoreTS, TCP READ and WRITE failure with a variety of error codes: RDP_TCP: An error was encountered when transitioning from StateUnknown in response to Event_Disconnect (error code 0x80070040).

TCP socket READ operation failed, error 64

TCP socket WRITE operation failed, error 64

and also this error The RemoteFX protocol connection RDP-Tcp#0 encountered an error (0x80004004)

7. Done

Answer 4

The problem has persisted even after your suggestions.

TerminalServices-LocalSessionManager logged this error message at about the time I couldn't reconnect to the server:

An error occurred when transitioning from CsrConnected in response to EvCsrInitialized. (ErrorCode 0x80070057).

Thanks, Niko

Answer 5

Hello，

Error codes 0x80070057 are usually related to incorrect configurations or parameters, perhaps because some settings were not applied correctly.

1. Make sure RDP's SecurityLayer and UserAuthentication settings are correct:

Open the registry editor (regedit.msc), navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp, and make sure that both SecurityLayer and UserAuthentication have values of 0. If the registry is modified, restart the server for the changes to take effect.

2. The RDP self-signed certificate may be corrupted or expired, causing connectivity issues. You can try regenerating the certificate:

Open the Certificates management console (certlm.msc) in Administrative Tools, navigate to Remote Desktop > Certificates, delete the existing RDP self-signed certificates, and restart the Remote Desktop Services service.

3. In the client's RDP file (mstsc.exe), make sure that the "Reconnect if connection is interrupted" option is enabled. Open the Credential Manager and delete the RDP credentials associated with the remote host.
4. It could be that the server is enforcing the use of FIPS-compliant algorithms, which is causing the remote connection issue. You can disable it using Group Policy:

Open the Group Policy Editor (gpedit.msc) and navigate to: Computer Configuration> Windows Settings> Security Settings> Local Policies >Security options. In the right pane, double-click System Encryption: Encrypt, Hash, and Sign with FIPS-Compliant Algorithms, click Disable, and then click OK. Restart the server.

远程协助连接不起作用 - Windows Server | Microsoft Learn

5. If the server is joined to a domain, make sure that it can communicate with the domain controller.
6. If you're using a VPN connection, try disabling the VPN and reconnecting.

Best regards,

Jingjing Wu