The DC you are communicating to is for cust.net or a subdomain. The error code states that is not able to resolve the object and refers to somecust.com for resolve. The DC only has the database for cust.net, not somecust.com. It is possible that you could get the information PM needs when pointing it to a Global Catalog Server and use port 3268 for LDAP instead of 389. This is not a documented and supported option, so no guarantees that this actually will work. Officially only one domain to store the users and groups is supported. I hope this helps.
FrankMS
26 Posts
0
August 27th, 2018 07:00
Hello,
The DC you are communicating to is for cust.net or a subdomain. The error code states that is not able to resolve the object and refers to somecust.com for resolve. The DC only has the database for cust.net, not somecust.com. It is possible that you could get the information PM needs when pointing it to a Global Catalog Server and use port 3268 for LDAP instead of 389. This is not a documented and supported option, so no guarantees that this actually will work. Officially only one domain to store the users and groups is supported. I hope this helps.
Regards
Frank