|
To avoid possible problems in the process of synchronizing and authenticating users in a domain, it is possible to test your configuration through the SE Configuration component  Authentication (CM008) Directory integration Domains section. On the domain data screen, click on the " " button.
This procedure will test the communication of the SE Suite server with the authentication and directory servers informed in the configuration. The tested protocols are LDAP (which will use the provided connection string, username and password, and communication with the domain address) and NTLM v2 port (for NTLM v2 protocol authentication).
Connection test failure usually occurs if there are errors in domain configuration or problems in the network connections between the SE Suite server and the servers that host the directory and authentication services. Therefore, it is indicated the use of tools to perform connection diagnostics or the help of the network administrator, for possible verifications of addresses and ports used in the communication.
The following table will detail the possible errors that the connection test can show and how to resolve them. The messages are the same for the connection test via SE Suite and for connection testing via the SE Identity application and the solutions can be applied to both scenarios:
Return
|
Solution
|
Error message connecting to the domain controller
|
The SE Suite server was unable to make a connection via LDAP protocol using the URL entered in the "Connection String" field. Verify if the field is filled correctly and if a port has not been specified in the URL itself, verify if the server is accepting connections on the default LDAP port 389, or for ports 636 and/or 3269, defaults to LDAPS, or contact administrator to check the availability of the service.
|
Alert message stating that the connection via NTM nv2 failed
|
The SE Suite server was unable to open a connection to the domain and port address reported in the configuration. Verify if the respective fields ("Domain address" and "NTLM v2 port") are correct and if the destination server is accepting connections on the port informed. If it is not, check the firewall rules or contact the administrator of your network. Note: If you do not intend to use the NTLM v2 authentication protocol, this alert can be ignored.
|
Error message informing that the user was not found or the password is incorrect
|
Communication with the directory service occurred without problems, but the user and password entered in the "User" and/or "Password" fields are incorrect. This user refers to a user record in the directory service, so it must be verified if the name and password are in accordance with the information recorded in the service. Remember that in the "User" field the name must be entered, not the login.
|
Alert message stating that NTMLv2 authentication failed
|
In this case, the "User Login" (example: user.test@domain.local) and/or the "Password" entered is incorrect. The user in question is also a recorded user in the directory service, just check if the information is correct. Note: If you do not intend to use the NTLM v2 authentication protocol, this alert can be ignored.
|
|
