Step1. install client software
When you log on to CentOS from a local Windows server, you must use the client software to establish a connection.
We recommend that you use the SecureCRT and putty clients to log on.
Install the SecureCRT client on the local machine and start the client.
Step 2. Log on to the CentOS ECS instance
1. after completing the client configuration, click "file"> "connect" to open the "connection" dialog box and click "New session" in the dialog box to open the new session wizard, select "SSH2" as the protocol, as shown in the following figure:
2. Click "next" and configure as follows in the session Wizard:
(1) host name: enter the public IP address of the ECS instance (you can view the public IP address of the ECS instance on the ECS "management view" page ).
(2) Port: Enter the ECS port, which must be 22.
(3) User Name: Enter the administrator account.
As shown in the following figure:
3. Click "next" to confirm the name of the session (the default is the previous ECS public IP address). Click "finish" to create a session.
4. In the "connection" window, right-click the newly created session and select "properties". In the "session options" pop-up window, deselect the "public key" check box, as shown in the following figure:
The public key is not authenticated, so you need to deselect the "public key" check box ".
5. In the session list in the "connection" window, you can view the previously created session. Click "connect" to connect to the CentOS ECS instance, as shown in the following figure:
6. In the pop-up "PAM authentication Authentication" dialog box, enter the password, which is the password of the administrator account. Click "OK" to complete the logon.
As shown in the following figure:
Note:
The initial password of the administrator account is assigned by the system. You can reset the password. For more information, see reset the password of the administrator account.
7. Choose Options> session Options> terminal to open the terminal settings dialog box and set the sending protocol, as shown in the following figure:
When the network environment is normal, configure the "sending protocol" in "anti-idle" to keep the terminal connected to the stepping stone or server, and keep the session continuously open when no operation is idle.