Failed to Log In to the Client, and the System Prompts for Connection Failure

Publication Date:  2012-07-19 Views:  224 Downloads:  0
Issue Description
The client cannot be logged in to, and the system prompts "Connection failed in user login". The Details part in the dialog box describes the basic measures to locate the fault.
Alarm Information
None.
Handling Process
l           Cause 1: The security mode on the client is inconsistent with that on the server.
1.         Log in to the server as the administrator.
2.         Click Start > Run, and enter the cmd command to open the CLI. Run the ssl_adm -cmd query command to query the communication mode used by the current server.
If the information is displayed as:
DS communication mode is common. 
The current communication mode is common.
the current server is in its common communication mode.
If the information is displayed as:
DS communication mode is ssl. 
The current communication mode is ssl.
the current server is in its security communication mode (SSL).
3.         Check the communication mode in the client login window. If the communication mode displayed does not comply with that on the server, modify the configurations on the client to comply with the mode on the server.
l           Cause 2: The connection to the server is abnormal.
1.         Choose Start > Run, and enter cmd to open the CLI on the client.
2.         Run the following commands to check whether the connection is successfully established between the client and the server:
> ping -t server_IP_address
3.         If the connection fails, check the network connection.
l           Cause 3: The status of the server is abnormal or the version is incorrect.
1.         Log in to the server as the administrator.
2.         Click Start > Run, and enter services.msc.
3.         Check whether the iMapService service is started or not in the Services window. If it is not started, right-click on that entry, and select Start to start the iMapService service.
4.         Log in to the VSM client on the server.
5.         Click Help > About in the main menu to open the About dialog box, and check the VSM version.
6.         If the client software version on the client does not comply with the client software version on the server, please reinstall the client software on the client to make it comply with the client software on the server.
l           Cause 4: The port on the server is unreachable.
1.         In the login window on the client, click ... following Server.
2.         Check whether the port number of the server is correct in the server list.
?       When the communication mode is Common, the port number is 31037.
?       When the communication mode is Security, the port number is 31039.
3.         If the port number is incorrect, change it to the correct one.
l           Cause 5: The SSL certificate has expired.
If the communication mode applied on the server is Security(SSL), contact the technical support personnel to check whether the SSL certificate has expired.
l           Cause 6: The number of online clients exceeds the upper limit.
For details, see 5.13 Number of Connections Reaches the Maximum Limit During Login to a Client.
Root Cause
The possible causes are as follows:
l           Cause 1: The security mode on the client is inconsistent with that on the server.
l           Cause 2: The connection to the server is abnormal.
l           Cause 3: The status of the server is abnormal or the version is incorrect.
l           Cause 4: The port on the server is unreachable.
l           Cause 5: The SSL certificate has expired.
l           Cause 6: The number of online clients exceeds the upper limit.
Suggestions
None

END