This topic provides answers to frequently asked questions about how to connect to a simple application server.

What do I do if I am prompted that the connection has timed out when I connect to a simple application server outside mainland China?

If you are in mainland China and attempt to connect to a server in a country or region outside mainland China, latency and packet loss may occur, which causes the server to be inaccessible. This is a problem with the Internet service providers and cannot be solved on the server. For information about the regions where Simple Application Server is supported, see Regions and network connectivity. You can use one of the following methods to solve this problem:
  • If the network inaccessibility problem is not a consistent problem, you can change the local network environment or try to connect to the server later.
  • If your server is not required to be deployed in a country or region outside mainland China, we recommend that you request a refund for your server and purchase a server deployed in mainland China.
    Note If you cannot request refunds for servers, submit a ticket.

What do I do if the connection to a Linux server fails when SELinux is enabled on the Linux server?

For information about how to solve this problem, see What do I do if an SSH remote connection exception due to SELinux being enabled occurs on a Linux instance?

If Security-Enhanced Linux (SELinux) is enabled, system security can be enhanced. However, after SELinux is enabled, the files of the operating system are damaged, and failures occur on system startup. We recommend that you enable or disable SELinux in an appropriate manner to avoid system startup failures. For more information, see Enable or disable SELinux.

What do I do if an authentication problem occurs when I connect to a Windows server?

This problem may be caused by upgrade patches released by Windows. For information about how to solve this problem, see the following topics:

What do I do if I cannot connect to a Windows server by using the Administrator account?

If you configure security policies on your Windows computer to deny logons from terminal services, you cannot use Remote Desktop Connection (RDC) on your Windows computer to connect to a Windows server by using the Administrator account. For information about how to solve this problem, see What do I do if I cannot connect to Windows by using the Administrator account?

How do I troubleshoot the failure to connect to a Windows server while no error message appears?

This problem occurs when you use the RDC tool on your Windows computer to connect to a Windows server. This may be because remote connection permissions are not enabled on the Windows server. In this example, Windows Server 2012 R2 64-bit is used to describe how to solve this problem.
  1. Use the Simple Application Server console to connect to the Windows server.

    For more information, see Use the Simple Application Server console to connect to a Windows server.

  2. Open This PC. In the left-side navigation pane, right-click This PC and select Properties.
  3. In the left-side navigation pane of the System page, click Remote settings.
  4. In the Remote Desktop section of the System Properties dialog box, select Allow remote connection to this computer.
  5. Click Apply. Then, click OK.

    After the configurations are complete, you can try to connect to the server again.

What do I do if the "The remote computer that you are trying to connect to requires Network Level Authentication (NLA)" message is prompted when I connect to a Windows server?

When you use the RDC tool on your Windows computer to connect to a Windows server, the message may be prompted. This may be because the RDC tool on your computer is of an earlier version. In this example, Windows Server 2012 R2 64-bit is used to describe how to solve this problem.
  1. Use the Simple Application Server console to connect to the Windows server.

    For more information, see Use the Simple Application Server console to connect to a Windows server.

  2. Open This PC. In the left-side navigation pane, right-click This PC and select Properties.
  3. In the left-side navigation pane of the System page, click Remote settings.
  4. In the Remote Desktop section of the System Properties dialog box, clear Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended).
  5. Click Apply. Then, click OK.

    After the configurations are complete, you can try to connect to the server again.

What do I do if the "The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer" message is prompted when I connect to a Windows server?

For information about how to solve this problem, see What do I do if the "The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer" error message is prompted on the remote desktop of a Windows instance?

What do I do if I cannot connect to a Windows server and the server cannot access the Internet?

A possible cause of this problem is that network interface controllers (NICs) are disabled on the Windows server. In this example, Windows Server 2012 R2 64-bit is used to describe how to solve this problem.
  1. Use the Simple Application Server console to connect to the Windows server.

    For more information, see Use the Simple Application Server console to connect to a Windows server.

  2. In the lower-right corner of the desktop, right-click the Network icon network icon and select Open Network and Sharing Center.
  3. In the left-side navigation pane, click Change adapter settings.
  4. Find the disabled network, right-click the network, and then select Enable.
  5. After the network is enabled, right-click the network and select Properties.
  6. In the This connection uses the following items section, click Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  7. On the General tab, click Obtain an IP address automatically, click Obtain DNS server address automatically, and then click OK.

    After the configurations are complete, you can try to connect to the server again.