Server Remote Connection Prompt Client cannot connect to remote computer due to protocol error

Tips when connecting to the server remotely today

Interrupting remote desktop connections --------------------------- Due to protocol error The client cannot connect to the remote computer. Please reconnect to the remote computer. If the client still cannot connect, please contact your network administrator.

Error reporting when connecting to the server using Remote Desktop: The session will be interrupted due to a protocol error. Please reconnect to the remote computer. I thought it was a general error of the server, thinking that restarting the server would solve the problem, so the machine room restarted the server. No matter how to try the problem is still old, and then use other computers to try to connect, or the same problem, but had no choice but to let people go to the computer room to install a PCAnywhere is not willing to use PCA, after all, WINDOWS comes with a remote desktop is still a lot more convenient, so use PCA Log in to the server and double check.

Finally found an error in the system log: the terminal server authorization grace period has passed, the service has not been registered with the licensed license server. To continue, you need a terminal server license server. If you do not have a license server, the terminal server can run for 120 days after the first boot.

This reminds me that the server was not installed by myself at the time. It may be that the person who installed the system installed the "terminal server component". This service requires MS authorization. Generally, the system uses the remote desktop. "On the way, remote desktops can log in to two remote users at the same time, and "terminal server components" can have multiple users, but two remote users are generally enough, the terminal server can only use 120 days, 120 days later You need to register.

Then uninstall Terminal Services (Control Panel - Add or Remove Programs - Add or Remove WINDOWS Components - Cancel "Terminal Server" and "Terminal Server Authorization"), then restart the computer and then turn it on Remote Desktop (My Computer--Properties--Remote--Check "“ Enable Remote Desktop for this computer"), how to reconnect or report the same error. Finding various solutions from the Internet will not work.

When I was about to give up, I suddenly thought that since it was reported, "problem error", if modifying the remote port will solve the problem, try again. . . Open the registry, modify the PortNumber under [HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\Wds\ dpwd\\Tds\\tcp] to the required port, and then modify [HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Terminal Server\\WinStations\\RDP -Tcp] under PortNuber (this step is very critical, under normal circumstances there is RDP-Tcp folder in the registry, but now there is no such folder on the server, so export this part of the registry on other computers, then Import this server), modify the PortNuber port number, restart the server, and finally the familiar login interface appears again. . . .