:What do I do if issues occur when I use Workbench to connect to a Windows instance over RDP?

Check the RDP port of the Windows instance. For more information, see the View the port for Remote Desktop on a Windows instance section of the "How do I view and change the default port for Remote Desktop on a Windows instance?" topic.

• The port is not port 3389.

  Connect to the Windows instance over RDP by using the RDP port used by the instance.

• The port is port 3389.

  Proceed to the next step.

Check the security group settings of the Windows instance to determine whether the RDP port is open. For more information, see View security group rules.

• The RDP port is not open.

  To allow Workbench connections to the port, add a security group rule to a security group of the instance based on the preceding table. For more information, see Use Workbench to connect to a Windows instance over RDP.

• The RDP port is open.

  Proceed to the next step.

Check whether the firewall is enabled for the Windows instance and whether the firewall denies Workbench connections to the RDP port. Perform the following steps:

1. Connect to the Windows instance by using Virtual Network Computing (VNC). For more information, see Connect to an instance by using VNC.

2. Check the status of the firewall. For more information, see Enable or disable the Windows firewall.

   • If the firewall is enabled, disable the firewall and use Workbench to connect to the instance.

   • If the firewall is disabled, proceed to the next step.

Check whether third-party security management software, such as Safedog, is installed on the Windows instance and whether the software disables logons of specific users.

• Third-party security management software is installed and disables logons of specific users.

  Remove the restrictions on logons of specific users and use Workbench to connect to the instance.

• Third-party security management software is not installed or the software is installed but enables logons of specific users.

  The Windows instance may be configured with other system settings that disable logons of specific users. We recommend that you use VNC to connect to the instance. For more information, see Connect to an instance by using VNC.

Check whether the username that you entered is Administrator.

• The username is not Administrator.

  The default username of RDP in Windows is Administrator. If you did not change the default username, use Administrator to connect to the instance.

• The username is Administrator.

  Proceed to the next step.

Check whether you entered the correct username and password in Workbench.

• The username or password is incorrect.

  If you manually entered the username and password, typos may exist. Check the username and password that you entered.

  Note

  The misspelling of Administrator is one of the most common reasons that cause connection failures.

• You forget the password.

  Reset the password and use the new password to connect to the instance. For more information, see Reset the logon password of an instance.

• The username and password are correct.

  Proceed to the next step.

If you modified the local security policy of the Windows instance, check whether the local security policy disables logons of specific users. For more information, see the "Solution 1: Modify the local security policy" section in What do I do if the error message that indicates lack of Terminal Server User Access permissions appears when I connect to a Windows instance by using Remote Desktop?

• The local security policy disables the logon of the user that you use.

  Remove the user from the local security policy and use the user to connect to the instance.

• The local security policy is not changed or the local security policy does not disable logons of specific users.

  Proceed to the next step.

If you used a non-Administrator user to connect to the instance, check whether the user is a member of the Remote Desktop Users group. For more information, see the "Solution 2: Grant the logon permissions to general users" section in What do I do if the error message that indicates lack of Terminal Server User Access permissions appears when I connect to a Windows instance by using Remote Desktop?

• The user is not a member of the Remote Desktop Users group.

  Add the user to the Remote Desktop Users group and connect to the instance as the user.

• The user is a member of the Remote Desktop Users group.

  The Windows instance may be configured with other system settings that disable logons of specific users. We recommend that you use VNC to connect to the instance. For more information, see Connect to an instance by using VNC.