Configuring computer name resolution

If user access problems still occur after configuring the Meridian service account as described in Granting membership query access, the problem could be caused by incorrect computer name resolution.

Note    You can confirm this cause by testing whether vault access works for the remote domain users as long as no roles are applied in the vault. You can also test this by creating a temporary test vault. As soon as roles are applied to the vault, users in remote domains can no longer access the vault. Only users from the home domain (the domain where the Meridian application server resides) can access the vault.

If the Meridian application server is not able to find a domain controller for the remote domain, add the fully qualified remote domain to the DNS suffix list for the TCP/IP protocol of the Meridian application server’s active network card.

Other conditions that can cause this behavior include:

• The remote domains are not configured as described in Understanding Active Directory security problems.
• Settings on firewalls between the domains.