Even if the required permissions do exist, the local administrator account probably does not have the same password as the domain administrator account, so the logon won't be successful. Odds are that the local administrator account lacks the permissions to log on to the machine remotely. If the IT pro types Administrator instead of PoseyLab\Administrator, then the client would attempt to log in using the endpoint's local administrator account rather than the domain administrator account.
One of the more common mistakes is to accidentally omit the domain name from the credential set.Ĭonsider an IT professional logging in with an administrator account for the example domain PoseyLab.
This includes making sure that the credentials are entered in the correct format and have the correct capitalization, as well as any other considerations. The first step in troubleshooting the problem should always be to make sure that the correct credentials are in place. If these steps don't yield a successful RDC connection, then IT administrators should take troubleshooting steps to determine and address the root cause of the issue. Otherwise, the client prompts you to enter a username and password. If the RDP client has saved credentials on hand from a previous session, then the new session automatically uses them. Then, it's as simple as clicking the Connect button to establish the session.
Admins only need to open the Remote Desktop client - also known as the RDP Client or the Remote Desktop Connection (RDC) app - and enter the name or IP address of the endpoint that will host the connection. When everything is working properly, establishing a remote desktop session is a simple process. Fortunately, troubleshooting the problem is usually a straightforward process. For example, administrators may find that the remote machine refuses the Remote Desktop Protocol ( RDP) connection.
0 kommentar(er)
