What should I do if I can't connect to Windows ECS remote login?

1. Check whether the Elastic IP can be pinged successfully.

If not, please see "Elastic IP Ping Fails" below to check.

If the EIP can be pinged, go to Step 2.

2. Check whether port 3389 of the Elastic Cloud Server can be accessed.

If port 3389 cannot be accessed, check whether port 3389 is allowed in the security group.

If it can be accessed, go to Step 3.

3. Check whether the RDP service in the Elastic Cloud Server is abnormal.

Log in to another Windows cloud server in the same Intranet CIDR block and remotely log in to the faulty cloud server on this server.

If the remote login fails, the RDP service may be abnormal. Log in to the faulty cloud server using VNC to check whether the RDP service is abnormal. Then, restart the RDP service, and try to connect again.

Restart the RDP service as follows:

· Click Start, select Run, and enter services.msc.

· In the list of services, select Remote Desktop Services and restart the service.

4. Check whether Elastic Cloud Server modifies the remote connection port.

5. Check

whether the configured port is the default 3389 under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStation s\RDP Tcp\PortNumber. If not, change the port to the configured one when connecting remotely.

6. Check whether the Elastic Cloud Server limits the number of connections.

Check the remote desktop configuration inside the OS:

· Click Start, select Run, and enter gpedit.msc to open Group Policy Editor.

· Select Computer Configuration > Manage Templates > Remote Desktop Services > Remote Desktop Session Host > Connect, enable Limit the Number of Connections to see whether the limit is enabled.

Note: If the maximum number of connections is configured here, it may cause Windows remote login to be unable to connect. If multiple users are logging in to the server at the same time, and the number has exceeded the maximum number of connections, users outside the maximum number cannot receive arbitration from the server, causing the session to remain in the Configuring state. Please select to disable the configuration or set a larger maximum number of connections.

When logging in to the cloud server remotely via VNC, what happens if the cloud server is remotely logged in by others via VNC at the same time?

Both users can log in to the VNC and the actions will affect each other.

Why do I use VNC to log in remotely and try to copy local characters to send to the virtual machine, but find that I can't reach the 3000 characters described at one time?

This may be caused by the following two reasons:

1. The server was purchased earlier, and users need to manually synchronize and upgrade this feature. The specific upgrade method requires the user to shut down the virtual machine and restart it to complete the update. Before shutting down the server, please save your data to prevent data loss.

2. The following server specifications do not support 3,000 characters, only up to 160 characters, the actual new situation is subject to the console:

Cloud server: s2

GPU cloud server: P2v, G5, PI2, G6, P2vs, G5s

Elastic IP Ping Fails

1. Check the security group rules. Check whether the security group corresponding to the ECS NIC allows the ICMP rule in the Inbound direction. You can meet any of the following rules.

2. Check the Network ACL rules.

1) Currently, eSurfing Cloud has launched the Network Access Control List (ACL) feature, you need to check whether it is enabled.

Check the status of Network ACL, as shown in the figure below, which indicates that Network ACL is currently enabled and disabled.

2) Check whether the NIC bound with elastic IP address belongs to the subnet associated with Network ACL, as shown in the figure below.

Associated subnet:

Inbound:

Outbound:

3) If the Network ACL is in Enabled state, you need to add ICMP release rules for traffic releasing.

Note: It should be noted that the default rule of Network ACL is to discard all inbound and outbound packets. If Network ACL is disabled, its default rule are still in effect.

3. Confirm whether the default route exists in the Elastic Cloud Server.

1) Log in to the Elastic Cloud Server and execute the following command to check whether a default route exists.

ip route

2) If the route does not exist, execute the following command to add a default route.

ip route add default via XXXX dev eth0

Note: XXXX indicates the gateway IP.

1. Perform ping test on servers in the same region.

When you try to ping the elastic public IP of the Elastic Cloud Server in the same region but fails, if it can be pinged successfully, it means that the virtual network is normal, please contact basic network technical support.

5. Use the webmaster tool for ping test.

1) Visit the webmaster tool website at http://ping.chinaz.com/122.112.197.21.

2) Enter the Elastic IP and click Ping Check.

3) If most monitoring points can be pinged, please check the local network.

6. Check the traffic monitoring of the Elastic IP in Cloud Eye.

Enter the Cloud Eye console to check the traffic of the Elastic IP and check if the bandwidth of the IP is full.

7. Internal troubleshooting of the Elastic Cloud Server.

1) Confirm whether the Elastic Cloud Server is multi-NIC, if it is and the Elastic IP is bound to a non-master NIC, you need to configure policy-based routing inside the Elastic Cloud Server.

2) Log in to the Elastic Cloud Server and check whether the NIC is created and whether the NIC obtains a private IP address. If you cannot log in to the Elastic Cloud Server using the password set by the user, contact the technical support personnel responsible for the image to obtain the default password.

3) If the NIC is not created correctly, contact the technical support personnel responsible for the operating system to troubleshoot.

4) If the NIC has been created, but the private IP address has not been obtained, please refer to Cloud BU Knowledge Base Template - Troubleshooting Methods - (DHCP Cannot Obtain Intranet IP Normally) for troubleshooting.

5) Execute the command top to check whether the CPU usage of the Elastic Cloud Server rises.

6) If the operating system of the Elastic Cloud Server is linux, execute the command iptables-save to check whether the Elastic Cloud Server is restricted by internal security rules.

7) If the operating system of the Elastic Cloud Server is Windows, please check whether there is any restriction on the firewall of Elastic Cloud Server.

8. Port Failure Troubleshooting.

1) If there is no problem with the ping test of the Elastic Cloud Server, but the access to a specific port is not available, and the port is within the range shown in the figure, the user needs to change the service port because the following ports are blocked by the operator.

2) If you cannot access a specific port of the Elastic Cloud Server, you need to check whether the security group rules and the Network ACL are released for the service port.

3) Log in to the Elastic Cloud Server and execute the following command to check whether the Elastic Cloud Server is listening on this port.

netstat – na | grep

Note: XXX indicates the port number.