Troubleshooting: Data Tab Test Connection Fails

Version Affected: All
 
 

Overview

This article explains how to resolve two causes of the Data tab's Test Connection button failing.

• See Cause 1 - If the Test Connection button fails on an LDAP over SSL connection specifically, and the realm otherwise appears to work.
• See Cause 2 - If Test Connection fails with "Unknown error (0x80005000)", and logging in gives "Invalid User."

These causes are not related, so a fix for one cause will not resolve the other cause.

 

In this article

• Cause 1: Test Connection Uses Different Logic for SSL
• Cause 2: Invalid LDAP Connection String

Cause 1: Test Connection Uses Different Logic for SSL

During an SSL connection, the Test Connection button uses slightly different logic than the realm itself uses to connect. Because of this, the button can fail even when the realm's actual connection is working correctly.

Resolution 1:

To resolve this:

1. Don't rely solely on the Test Connection button to confirm whether the connection is truly established. Test the realm itself instead.
2. If possible, also test whether a regular (non-SSL) secure connection works, to help isolate whether the issue is specific to SSL.

Cause 2: Invalid LDAP Connection String

The LDAP connection string entered on the Data tab is invalid.

Resolution 2:

To resolve this, correct the LDAP connection string. Valid formats include:

1. To talk to a specific Domain Controller (DC):
   

   LDAP://servername.domain.com/dc=domain,dc=com

2. To talk to any DC in the domain:
   

   LDAP://domain.com/dc=domain,dc=com

3. To talk to the Global Catalog server:
   

   GC://servername.domain.com/dc=domain,dc=com

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.