Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > NPM 12 Advanced AD settings

NPM 12 Advanced AD settings

Table of contents

Updated August 22, 2016


The new Advanced AD settings with LDAP supports implementation that allows authenticating users from a single domain. If you are authenticating users from multiple domains this will not work. You will need to use MSAPI which is the standard method that has always been part of NPM. 



NPM 12



When SSL is used (then LDAP is used) and the default port is 636.If using SSL/TLS, the preferred port is 636. This port requires SSL/TLS, and if the SSL/TLS negotiation is not working, the connection will not complete. To ensure proper security when using port 389, use LDAP connection (without SSL). 

If you want to see objects from multiple domain in the AD forest with a single LDAP connection, the SSL/TLS port for that “global catalog” directory is 3269. Changing the port to 3269 and the Domain DN to DC=example,DC=ex,DC=us will allow you to search, but only the exampleexus domain, regardless of what domain you type in the search field.


If you are looking to do multiple domain, please contact support so a feature request can be submitted to development.  




Last modified