Determining if the main and failover LDAP servers are runningDescription<!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } --> Determining if the main and failover LDAP servers are running ProblemUsers are able to access the instance, but it takes longer than expected. Symptoms User authentication is delayed.There is an unexpected behavior when attempting to log in. CauseIf the instance is configured with multiple IPs during LDAP server configuration, there may be an issue when one of the servers is not accessible.See Specify Redundant LDAP Servers for information on redundant LDAP servers. Resolution Verify with the LDAP administrator that the configured LDAP servers are available.Update the LDAP server configuration to list only one IP in the Server URL field, noting how long it takes for the user(s) to be authenticated.If IPs are listed in the Server URL, try using the FQDN instead.Contact the network administrator to verify that the VPN and/or firewalls are configured correctly. If the suggestions above did not resolve the issue, create an incident (INT) ticket, and include this information: The network administrator contact informationThe result of nslookup / host of the affected instance from the LDAP server(s)The result of ping / traceroute from LDAP servers to the instance URL, noting the start and endpoint IPs.The result of packet captures that can be opened in Wireshark, noting the start and endpoint IPs, and the time frames when the user authentication was requested.