Remote desktop connection is divided into two stages: \x0d\ The first stage is the Unicom of RDP protocol, during which the identity of the server will be verified, that is, the interface you see. Windows server uses certificate authentication. There are two requirements for certificate authentication: \x0d\ 1. The certification authority must be the root certification authority in your computer in order to issue a valid certificate. However, the default certificate of your computer is a self-signed certificate, not a certificate issued by an authoritative organization, and you will report it to an "untrusted certificate authority", but this will not affect his SSL encryption signature function, so it will not affect the security of communication; This feature is used to prevent you from connecting to the phishing server. For example, I used DNS cache pollution, so that you unconsciously logged into a fake server and cheated your password. Then if your server is an SSL certificate from an authority, you can immediately find that the certificate is wrong. \x0d\2。 The domain name when accessing the server is exactly the same as your machine name. In other words, your machine name is aaa.bbb.com, so when you visit him, the domain name must also be aaa.bbb.com. If you use a different name or IP address, you will be prompted "Wrong server name". \x0d\ Stage 2: After protocol connection (warning can be ignored in the first stage), it will begin to verify whether your account and password match the account accessing the remote desktop. \x0d\ So if the account password is wrong, first check whether the account passwords are completely consistent, and then check whether the account permissions allow remote access.