Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Cannot authenticate to remote DPA instances from a Central DPA using AD/LDAP

Cannot authenticate to remote DPA instances from a Central DPA using AD/LDAP

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 925 Votes: 0 Revisions: 11


You cannot authenticate to a remote DPA instance from the DPA Central Server. This can happen in the following cases:

  • The DPA Central Server cannot connect to your AD/LDAP domain server.
  • The credentials supplied are invalid.

This is a side effect of one of our anti-lockout features for AD/LDAP. Many AD/LDAP servers are configured to lock out user accounts for failed passwords. To avoid locking accounts, we don't try to log on to any remote instances using AD/LDAP if you don't log on to the Central DPA with a valid AD/LDAP credential first.


  • Log on to the Central DPA using valid AD/LDAP credentials.
  • Log on to each remote DPA instance separately without using the Central DPA.
  • If your AD/LDAP server does not lock out user accounts for failed password failures, you can configure your Central DPA instance to always attempt authentication with remote DPA servers:
    1. Edit the file <dpa>\iwc\tomcat\ignite_config\idc\
    2. Add the following line:
    3. Save the file and then restart the Central DPA. 


Last modified