Home > other >  Remote desktop can't log in
Remote desktop can't log in

Time:10-06

My computer use MSTSC remote enough other computer, A A computer in the company, my computer cannot remote login to, but others can can also remote computer A computer, how to solve, please answer

CodePudding user response:

Your network administrator isn't done to switch what configuration? If the computer itself do not have what problem

CodePudding user response:

Do you have A computer remote login permissions, still have even if you are win2012 xp is not remote access system, then there is your computer iP is A computer on the same network segment

CodePudding user response:

1, whether the same network segment?
2, the network is adjusted the route,
3, to simplify the GHOST system installation,
Interrupt the remote desktop connection client cannot be established with a remote computer connection,
The cause of this error may be:
1) remote connection may not be enabled on the remote computer,
2) it is more than remote computer maximum number of connections,
3) when the connection is established the emergence of a network error
The specific solution:
Sometimes this error message: due to network errors, connection is interrupted, please connect to the remote computer again. Remote connection I'm sure is opened, also open the firewall port 3389 inside, and connect to other server can connect, shows that the machine is no problem, I use scanning software, scanning the server, show the IP and port are exist, this server network is no problem, there is no way, only by constantly testing, later in the system log to see many system error messages, including: serious mistake "RDP protocol component" DATA ENCRYPTION "found an error in the deal flow and interrupt the client connection," the tortuous learned that this is because the Certificate in children is responsible for the communication terminal services authentication and ENCRYPTION of DATA information, once it is damaged, terminal services agreement components will be an error is detected, the interrupt communications between the client and the terminal server, some of the reasons for Certificate son key damage, such as some system administrators to install and uninstall software, such as unreasonable configuration parameters for terminal services, then we need to reset the key value of content, can repair the terminal services,
Reach the registry editor window, "HKEY_LOCAL_MA CHINE \ SYSTEM \ CurrentCon trolSet \ Services \ TermService \ Parame ters", named "Cer tificate" key, delete it, restart Windows XP, or Windows server 2000 server SYSTEM can regenerate the "Certificate" button, so that the client can normal connection to the terminal server,
After the terminal Server unable to connect problems, we first need to see whether it is network fault caused by detecting the remote client and XP system (Windows Server 2000 Server) is normally connected to the network; Then check the terminal server encryption level is set too high, elimination of these reasons, it is likely to be key damage the "Certificate", in addition, "HKEY_LOCAL _MACHINE \ SYSTEM \ Cur rentControlSet \ Services \ Term Service \ the Parameters" under "X509 Certificate" and "X509 Certificate ID" damaged may also lead to terminal Services appear problem, their repair method and the "Certificate" damage repair methods of the same key,
2
Prompt "local computer client access license cannot upgrade or update" solutions
1) open the registry editor, accused of machine in registry key HKLM \ SOFTWARE \ Microsoft \ MSLicensing, positioning to
2) backup MSLicensing button,
3) delete MSLicensing keys, restart the system,
Prompt "the client cannot connect to the remote computer,"
1) the remote computer unreachable (can't or blocked by a firewall)
(2) the server is not open port 3389 system properties in the "remote desktop" in the "remote" page not tick or not use a remote login user)
3) terminal services service did not start, start the service, there are two RDP service also don't forget to oh
4) check if the remote desktop has changed the port, step: open the "start -> run, type" regedit ", open the registry, enter the following path: [HKEY_LOCAL_MACHINE \ SYSTEM \
CurrentControlSet \ Control, Terminal Server, Wds \ RDPWD \ Tds, TCP], see PortNamber value? Its default value is 3389, if not, please change back,
  • Related