No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Check support SSL encryption cause TSM with AD domain linkage unsuccessful.

Publication Date:  2019-07-09 Views:  432 Downloads:  0

Issue Description

When the TSM (V1R2C06 version) do linkage configuration with AD domain, test the connection is not successful and prompt the user name and password error.

Alarm Information


Handling Process

Processing with possible causes:
1 On AD domain controller, use AD domain control browser to view the certification account settings and synchronization account, confirm the user name and reset your password. Re-synchronization is still unsuccessful. Rule out the first possible reason;
2 In the TSM server execute execution ping command to AD domain controller normally, ssh its port normally, eliminate question 2;
3 In the TSM on AD domain linkage configuration interface the support SSL encryption has been checked, perhaps this is the cause of the problem. Cancel the checked item, synchronous again successful. Problem is solved.

Root Cause

The possible reasons are as follows: 
1 The authentication account username and password used for synchronized error;
2 Can’t be properly connected to the AD domain server;
3 SSL encryption and other parameters do not match.
By the investigation confirm the cause of the problem is the third reason.


In the linkage process of TSM with other third-party authentication server, it must guarantee that parameters are completely consistent. Some third party server enable the SSL encryption, and some not to use. To this kind of circumstance, have a test in linkage. Two kinds of cases all have a try.