Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Determining if the main and failover LDAP servers are running - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Determining if the main and failover LDAP servers are running
KB0538724

Determining if the main and failover LDAP servers are running


1814 Views Last updated : May 1, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Determining if the main and failover LDAP servers are running 

Problem
Users 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.

Cause
If 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 information
  • The 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. 

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.