If the dialog box is empty (you cannot browse), but a red error message does not appear, the Pano Manager cannot communicate with the Domain Controller. To fix this problem, specify the port of the Global Catalog. For example: ldap://10.1.100.1:3268.
By default the Global Catalog runs on port 3268 in unencrypted mode and on 3269 in encrypted mode. Therefore, the URL is
ldaps://dirserver1.yourdomain.com:3269 for encrypted mode and
ldap://dirserver1.youdomain.com:3268 for unencrypted mode. Consult your Active Directory administrator if the Global Catalog runs on a different server or if it is configured to run on a different port.
If you are convinced that the Active Directory server address is indeed correct, try to enter the Global Catalog server address. [Global Catalog generally runs on port 3286]. If putting in Global Catalog address works, check to see if the Pano Manager is on the same domain as Active Directory domain controller whose address was entered. If not, then change it to same domain.
If you receive a “javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused]” exception, you might not have a service location record in your DNS Server.
If you have more than one domain controllers, Pano Manager can automatically choose one based on the workload on each domain controllers. However, sometimes this configuration gives this exception if you don’t have a service location record in your DNS server.
In order to properly establish a relationship between a user and a DVM the user must be able to be authenticated using a complete UPN (User Principal Name) that, in the end, gets passed along as something like the form of username@yourdomain.com.
The portion @domain.com is appended to the user name from information defined in the users account within Active Directory (or your alternate directory services database). If a
No UPN error is encountered, do the following:
To help troubleshoot configuration issues, the host URL and the following Root DSE attributes are written to the log after connecting. If above checks fail then get information about the exception in Pano Manager via the log file (go to
Work with Log Files):