Step 5-8 | There is no clear error message when the remote connection fails

Step 5: Check the firewall configuration

Note This troubleshooting can be performed only when the firewall is authorized to be disabled. Please confirm whether the firewall is closed, if not, fix it by adjusting the firewall configuration policy.

1. Use VNC to log in to the Windows instance.

2. Select Start > Control Panel in the menu bar.

3. Select the small icon as the viewing method, and click Windows Firewall.

4. On the Windows Firewall interface, click Advanced Settings.

5. Enable firewall configuration.

1) In Windows Firewall with Advanced Security, click Windows Firewall Properties.

2) Select Enabled (recommended), click Apply (A).

6. In Windows Firewall with Advanced Security, click Inbound Rules, pull to the bottom on the right side, right-click Remote Desktop-User Mode (TCP-In), and select Start Rules (E).

Step 6: Check Remote Desktop Services

You can check whether the remote desktop service is enabled on the Windows server system. The specific operation is as follows:

1. Use VNC to log in to the Windows instance.

2. Right-click the Start menu and click System.

3. On the system interface, click Remote Settings.

4. In the Remote Desktop area, select Allow remote connections to this computer (L), and click OK.

5. Start the Remote Desktop Services service.

In the Start menu, select Administrative Tools > Component Services > Services (Local), find the Remote Desktop Services service in the menu window on the right, check whether it is started, if not, start it.

start up

6. Load the drivers and services that Remote Desktop Services depends on.

In order to improve system security, sometimes some key services that Remote Desktop Services depends on are disabled by mistake, resulting in abnormalities of Remote Desktop Services. It can be checked by the following operations.

1) Right-click the Start menu, click Run, enter msconfig, and click OK.

2) In the System Configuration dialog box, click the General tab, select Normal Startup (N), and click OK. Normal start

3) Restart the ECS instance.

Step 7: Check the remote terminal services configuration

The failure to connect to the remote desktop of the Windows instance may be due to the following configuration exceptions of Remote Terminal Services.

NOTE This example uses Windows Server 2008 as an example. Operations of other Windows Server versions are similar.

Abnormality 1: The self-signed certificate on the server side is damaged

If the local client is a Windows 7 or later system, it will try to establish a TLS connection with the cloud server ECS. If the self-signed certificate used for the TLS connection on the ECS side of the cloud server is damaged, the remote connection will fail.

1. Use VNC to log in to the Windows instance.

2. Select Start>Administrative Tools>Remote Desktop Services>Remote Desktop Session Host Configuration.

3. In the Connections area, right-click RDP-Tcp, and then click Properties.

4. In the RDP-Tcp property window, change the security layer to RDP security layer, and click OK.

5. In the Operation area, click Disable Connection, and then click Enable Connection.

disable connection enable connection

Exception 2: The remote desktop session host configuration connection is disabled

Use the netstat command to query and find that the port is not listening normally.

After logging in to the Windows instance using VNC, it is found that the remote desktop RDP connection attribute configuration file is disabled. Re-enable the RDP-Tcp connection. For details, see Abnormality 1: The self-signed certificate on the server side is damaged.

Enable connection

Exception 3: Terminal server role configuration

When using remote desktop to access a Windows instance, the following prompt may appear.

This situation is generally caused by installing and configuring the terminal server on the server, but not configuring valid access authorization. You can refer to the following three solutions:

• Windows server remote desktop prompts "No remote desktop licensing server can provide a license" error

• When logging in to a Windows instance remotely, the error "The remote desktop user group does not have this permission" is reported

• If it is caused by the installation of the terminal server role, you need to log in to the server, right-click the computer, and select Role > Delete Role Service.

Step 8: Check the Network

1. If you cannot connect to the Windows instance remotely, you need to check whether the network is normal.

Use computer connection comparison tests in other network environments (different network segments or different operators) to determine whether it is a local network problem or a server-side problem.

• If it is a local network or operator problem, please contact the local IT personnel or the operator to solve it.

• If the network card driver is abnormal, reinstall it. Check the next step after troubleshooting the local network fault.

2. Use the ping command on the local client to test the network connectivity with the instance.

• When the network is abnormal, please refer to How to Capture Data Packets for Troubleshooting When the Network Is Abnormal.

• When the ping packet is lost or the ping fails, refer to Link Test Method When the Ping Command Is Lost or Unreachable.

• If intermittent packet loss occurs and the network of the ECS instance is always in an unstable state, see Using the ping Command to Test the IP Address of an ECS Instance with Intermittent Packet Loss to solve the problem.

3. Use the ping command in the instance to test the connectivity with the client. If a general failure error is displayed, please refer to the Windows instance pinging the external network address prompting "general failure" to solve it.