Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Database Performance Analyzer (DPA) > 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: 874 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