> Why can’t I browse the hierarchy even though my the Pano Manager is connected to Active Directory (AD)?
> Check the log by clicking the Log tab to see if there is a PartialResultException error or a Referral error. If there are errors present it might be necessary to specify the Global Catalog port at the end of the url string, e.g, ldap://ad.acme.com:3268. 3268 is for normal LDAP, 3269 is for secured LDAP.
> If you are able to successfully connect and browse the AD hierarchy after specifying the Global Catalog port, the problem might be due to one of the following issues:

> • | PartialResultException Errors: The domain the Pano Manager is on cannot reach the domain configured in the setup page. You can resolve this by setting the domain servers to refer to each other.

> • | Referral errors: The Active Directory host cannot communicate with another host it was referred to during the communication over LDAP because of the following possibilities:

> ° | The referred to host does not exist, cannot be reached, is behind a firewall, the user account provided in the setup page does not have access to read certain information, etc.

> ° | You have a complex Active Directory server configurations with multiple domains or sub-domains and shared groups (security or distribution). If you want to remove the Global Catalog port, you must identify the issue and fix it.

Did you find what you're looking for?
v2.5.1