If your server has the following error:
The RDP protocol component x.224 found an error in the protocol flow and interrupted the client connection. ”
There are 2 possible types of:
1: If you can continue to log on remotely, there may be a problem with your remote login component.
2: Someone attacks you, using brute force method to log into your system, resulting in system denial of service.
A word of caution against thieves!!
Workaround:
Set Group Policy ===== "management panel =====" Wndows components = = "Terminal Services!!
New additions (more ruthless solution, hehe.) ):
Event Type: Error
Event Source: TermDD
Describe:
The RDP "DATA Encryption" protocol component detected an error in the protocol flow and interrupted the client.
After online search data and analysis, it is the registry "Certificate" sub-key is corrupted, only to cause the user cannot with Terminal Services
For normal communication.
Analysis: Certificate sub-key is responsible for the authentication and encryption of data information in Terminal Services communication, and once it is corrupted, the Protocol group of Terminal Services
Detects an error and interrupts communication between the client and the Terminal server. There are many reasons for certificate sub-key damage, such as tube
The administrator installs and uninstalls certain system software, unreasonable configuration of Terminal Service parameters, etc. At this point we need to reset the contents of this key value,
To repair Terminal Services.
Workaround: Go to the Registry Editor window, expand
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters",
Locate the subkey named "Certificate", remove it, restart the Windows 2003 Server server, and the system will regenerate
Into the "Certificate" subkey so that the client can connect to the Terminal server normally.
The RDP protocol component x.224 found an error in the protocol stream and interrupted the client connection