Fixed: The RDP Protocol Component X.224 Detected An Error
This post mainly introduces fixes to “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client” problem. If you happen to encounter this problem, read this post to troubleshoot it.
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client
“In the office, I have a Windows 10 Pro PC. I connect to it remotely using RDP from within the same network. The clients remain connected for varying amounts of time (no more than one hour) before the session terminates and disconnects them at random. It is not due to inactivity that the disconnect happens. The user must wait for many minutes before being allowed to reconnect. I checked Event Viewer on Windows 10 Pro, it says:
Event ID: 50 The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
How can I fix this?”
Four methods to fix “The RDP protocol component X.224 detected an error”
Here in this part, we’ll introduce four methods to fix “The RDP protocol component X.224 detected an error” on Windows 10.
Method 1. Disable TCP chimney offload on both the client and the server
Step 1. Search for Command Prompt in the search box, and then choose Run as administrator.
Step 2. Type in the following command and then press Enter:
netsh int tcp set global chimney=disabled
Method 2. Disable RSS on both the client and the server
To disable RSS on both the client and the server, open Command Prompt using administrative credentials. Then type in the following command and then press Enter:
netsh int tcp set global rss=disabled
Method 3. Disable netDMA on the client and the server
Step 1. Press Win + R, type in “regedit”, and then press Enter.
Step 2. Navigate here: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > Tcpip > Parameters > EnableTCPA. If you don’t have this registry entry, right-click Parameters, choose New and then DWORD Value.
Step 3. Name the new value as EnableTCPA. Then double-click it to make sure its value data is set to 0.
Method 4. Change the Security Layer at the RDP stack to RDP
Step 1. Press Win + R, then type in “gpedit.msc” and press OK to open the Local Group Policy Editor.
Step 2. Navigate here: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.
Step 3. Find and click Require use of specific security layer for remote connections, then change its status to Enabled. Then choose RDP from the drop-down list as the Security Layer.
Error-free remote desktop software: AnyViewer
In addition to the above-mentioned four methods, another option for you is to use an error-free RDP alternative, for example, AnyViewer. AnyViewer is free and easy remote desktop software. It requires no complicated setup process. Users can easily get started with it.
It also provides users with unattended remote access. As long as both computers are logged in to the same account, you can easily connect one to another with one click. Let’s see how to make this happen.
Step 1. Download, install, and launch AnyViewer on both computers.
Step 2. Go to Log in, and then click Sign up. (If you already have signed up on its official website, you can log in directly.)
Step 3. Fill in the signup information.
Step 4. Then you can see you successfully logged in to AnyViewer. Your device will automatically be assigned to the account you've logged in to.
Step 5. Log in to the same AnyViewer account on the two devices, then click One-click control to achieve unattended remote access.
Conclusion
If unluckily, you happen to encounter “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client”, please try the four methods we mentioned in this post to troubleshoot it. Besides, you can also try a free and easy RDP alternative. Using AnyViewer to remotely access another computer will save you a lot of time and trouble.