Server remote connection prompt client cannot connect to remote computer due to protocol error
- 2020-05-06 12:03:25
- OfStack
Prompt
when connecting to the server remotely today
Disconnect the remote desktop connection to
---------------------------
The client was unable to connect to the remote computer due to a protocol error.
Please reconnect to the remote computer. If the client is still unable to connect, contact your network administrator.
Error connecting to server with remote desktop: session will be interrupted due to protocol error. Please reconnect to the remote computer.
This is thought to be a general error of the server, think that restart the server can solve the problem, so let the machine room restart the server. But no matter how to try the problem is still, and then try to connect with other computers, or the same problem, but had to let people to the computer room installed an pcAnywhere is not willing to use PCA, after all, WINDOWS came with the remote desktop is still much more convenient to use, so use PCA login to the server for careful inspection.
Finally, an error was found in the system log: terminal server authorization grace period has passed , the service has not yet registered with a licensed license server. To continue, you need a terminal server license server. Without a license server, the terminal server can run for 120 days after the first startup.
This remembered that the server is not pretended system at the time, may be installed system to the terminal server components installed, the service is need MS authorized, generally use the "remote desktop" line of the system, is the more remote desktop login two remote users, and the terminal server components can be multiple users, but two remote users generally fully enough, the terminal server can only be used for 120 days, 120 days need to register.
So unloading terminal services (control panel, add or remove programs, add or remove WINDOWS components -- cancel "terminal server" and "the terminal server license"), and then restart your computer and open the remote desktop (my computer - property - remote - check the "enable this computer remote desktop"), how to reconnect to try to the same fault again. Looking up all kinds of solutions from the Internet is no good.
When I was about to give up, I suddenly thought that since it is a "protocol error", if I modify the remote port will not solve the problem, try again... Open the registry and change PortNumber under [HKEY_LOCAL_MACHINE\SYSTEM\ Control\ Control\ Server\Wds\rdpwd\Tds\tcp] to the required port, Modify PortNuber under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Terminal \Terminal \Terminal \
\Terminal \
\Terminal \
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\ Finally the familiar login interface appears again...
when connecting to the server remotely today
Disconnect the remote desktop connection to
---------------------------
The client was unable to connect to the remote computer due to a protocol error.
Please reconnect to the remote computer. If the client is still unable to connect, contact your network administrator.
Error connecting to server with remote desktop: session will be interrupted due to protocol error. Please reconnect to the remote computer.
This is thought to be a general error of the server, think that restart the server can solve the problem, so let the machine room restart the server. But no matter how to try the problem is still, and then try to connect with other computers, or the same problem, but had to let people to the computer room installed an pcAnywhere is not willing to use PCA, after all, WINDOWS came with the remote desktop is still much more convenient to use, so use PCA login to the server for careful inspection.
Finally, an error was found in the system log: terminal server authorization grace period has passed , the service has not yet registered with a licensed license server. To continue, you need a terminal server license server. Without a license server, the terminal server can run for 120 days after the first startup.
This remembered that the server is not pretended system at the time, may be installed system to the terminal server components installed, the service is need MS authorized, generally use the "remote desktop" line of the system, is the more remote desktop login two remote users, and the terminal server components can be multiple users, but two remote users generally fully enough, the terminal server can only be used for 120 days, 120 days need to register.
So unloading terminal services (control panel, add or remove programs, add or remove WINDOWS components -- cancel "terminal server" and "the terminal server license"), and then restart your computer and open the remote desktop (my computer - property - remote - check the "enable this computer remote desktop"), how to reconnect to try to the same fault again. Looking up all kinds of solutions from the Internet is no good.
When I was about to give up, I suddenly thought that since it is a "protocol error", if I modify the remote port will not solve the problem, try again... Open the registry and change PortNumber under [HKEY_LOCAL_MACHINE\SYSTEM\ Control\ Control\ Server\Wds\rdpwd\Tds\tcp] to the required port, Modify PortNuber under [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Terminal \Terminal \Terminal \
\Terminal \
\Terminal \
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\
\ Finally the familiar login interface appears again...