Symptom
When trying to connect to a Windows instance remotely from Windows, you get the following message:
The remote desktop can't connect to the remote computer for one of the following reasons:
1. Remote access to the server is not enabled
2. The remote computer is turned off
3. The remote computer is not available on the network
Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
Possible Causes
Possible causes include but are not limited to the following:
The instance is in an abnormal status.
The CVM instance does not have a public IP or the public network bandwidth is 0.
The remote login port (3389 by default) is not opened in the security group bound to the instance.
Remote Desktop Services is not started.
Incorrect Remote Desktop settings
Incorrect Windows Firewall settings
Troubleshooting Directions
Checking instance status
2. On the Instances page, check whether the instance is "Running".
If no, start up the Windows instance.
Checking public IP
Check whether the CVM instance has a public IP in the CVM console.
Checking public network bandwidth
Check whether the public network bandwidth is 0 Mbps. At least 1 Mbps of public network bandwidth is required.
Checking remote login port (3389)
1. On the instance management page in the CVM console, click the target instance ID/name to enter its details page.
2. In the Security Groups tab, check whether the remote login port (3389 by default) is opened.
Checking remote desktop service
Note:
The following operations use an instance on Windows Server 2016 as an example.
2. Right-click and select System in the pop-up menu. 3. In the System pop-up window, select Advanced System Settings.
4. In the System Properties pop-up window, select the Remote tab and check whether the Allow remote connections to this computer is selected:
If no, select it and click OK.
5. Right-click
and select Computer Management in the pop-up menu. 6. On the left sidebar in the Computer Management window, select Services and Applications > Services.
7. In the service list on the right, check whether *Remote Desktop Services is started:
If no, start the service.
8. Right-click
and select Run in the pop-up menu. 9. In the Run pop-up window, enter msconfig and click OK.
10. In the System Configuration pop-up window, check whether Normal startup is selected:
If no, select it and click OK.
Checking Windows instance system settings
Note:
The following operations use an instance on Windows Server 2012 as an example.
2. Right-click and select Run in the pop-up menu. 3. In the Run pop-up window, enter services.msc and press Enter to open the Services window.
4. Double-click to open the Remote Desktop Services properties and check whether Remote Desktop Services is running as shown below:
If no, set Startup Type to Automatic and Service Status to Running (i.e., clicking Start).
5. Right-click
and select Run in the pop-up menu. 6. In the Run pop-up window, enter sysdm.cpl and press Enter to open the System Properties window.
7. On the Remote tab, check whether the Remote Desktop is set to Allow remote connections to this computer as shown below:
If no, set Remote Desktop to Allow remote connections to this computer.
8. Click
and select Control Panel in the pop-up menu. 9. In Control Panel, select System and Security > Windows Defender Firewall.
10. In Windows Defender Firewall, check the Windows Defender Firewall status as shown below:
If the status is On, proceed to Step 11. 11. In Windows Defender Firewall
, click Allow an app or feature through Windows Defender Firewall to open the Allowed apps window. 12. In the Allowed apps window, check whether Remote Desktop is selected in Allowed apps and features.
If no, select Remote Desktop to allow Remote Desktop through Windows Defender Firewall.
13. In Windows Defender
Firewall, click Turn Windows Firewall on or off to open the Customize Settings window. 14. In the Customize Settings window, set Private network settings and Public network settings to Turn off Windows Defender Firewall (not recommended) as shown below:
If you still cannot connect to the Windows instance on a remote desktop, please submit a ticket for assistance.
Was this page helpful?