This is caused by not accessing the AD server on the correct port for a multiple domain base DN search.
Using the "Browse Base DN" button in the administrative interface of PGP Universal Server allows you to view those other Base DN's, but if they are on a different domain than the LDAP/AD server that you are configured to synchronize with, it will fail to search and find the correct user in that Base DN.
Resolve this issue by changing the port used for LDAP lookups under the server entry in Consumers > Directory Synchronization to use port 3268 instead of port 389. You can also go to the Base Distinguished Name tab and sort the Base DN you are having trouble searching in and place it to the top of the list by setting it to 1 for the order. Click "View Sample Records" to verify that it shows the users in the correct Base DN that you are searching in.
PGP Universal Server
Managed PGP Desktop client
Active Directory (AD) Forest with multiple domains
Multiple Base DN configurations for each domain
Imported Document ID: TECH199479
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.