To view this website correctly, please ensure you have
JavaScript enabled.
Some of the website layout and links may not function properly with JavaScript disabled.
Skip to main content
Skip to first level navigation
For the following LDAP errors, GlobalScan NX (GSNX) writes more information about the error to the system log in the "Remarks" field. Below are the most common remarks, the most likely cause, and recommended troubleshooting steps.
Related Error No. and Error Message:
54020003 Address search has failed.
54020024 Connection test has failed.
-
Invalid LDAP(S) Server:
Remark:
javax.naming.CommunicationException: 192.168.0.100:389 [Root exception is java.net.ConnectException: Connection timed out: connect]
- Confirm that the LDAP(S) Server address is correct.
- Confirm the DNS settings. Are the AdminTool PC and the device setting using the same settings?
-
Invalid LDAP(S) Port No:
Remark:
Failed to initialize LDAP DataSource: javax.naming.CommunicationException: 192.168.0.100:390 [Root exception is java.net.ConnectException: Connection refused: connect]
- Confirm that the port is correct.
- Confirm the LDAP(S) server's firewall setting allows connections from GSNX.
- Try to connect using other LDAP tools.
-
Invalid User Name or Password:
Remark:
Failed to initialize LDAP DataSource: javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece ]
- Confirm that the proxy user is configured correctly.
- Confirm that the login user is inputting the correct information.
-
LDAPS Certificate Validation Failed:
Remark:
javax.naming.CommunicationException: 192.168.0.100:636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found]
- Confirm that the correct certificate is installed to the AdminTool (Configuration > System > Certificate) and then synchronize the device.
Note: GSNX verifies the LDAPS certificate before establishing the SSL connection in order to prevent a connection to a spoofed LDAP server. The verification is performed by comparing the SSL certificate stored in the AdminTool and the certificate sent from the LDAPS server. This means that these certificates must be completely identical.
-
LDAPS Configuration Failed:
Remark:
javax.naming.CommunicationException: 192.168.0.100:636 [Root exception is javax.net.ssl.SSLPeerUnverifiedException: hostname of the server '192.168.0.100' does not match the hostname in the server's certificate]
- Specify the LDAPS server name using the same fully qualified domain name (FQDN) as used by the imported certificate.
Note: GSNX also verifies the LDAPS server name configured in AdminTool and the hostname included in the certificate. So, use of the IP address in the AdminTool typically leads to a connection failure.
Your rating has been submitted, please tell us how we can make this answer more useful.
Answer
"54020003 Address search has failed." and "54020024 Connection test has failed." LDAP errors
Contact Information (required)
