What it means
The server refused a connection because the user or server is not allowed by the server access lists in its Server document.
Common causes
- The user is not in a group listed in the Access server field, or is in the Not access server (deny) list
- Nested groups, wildcards or Directory Assistance group lookups not resolving as expected
- A newly added group member not yet visible because directory views have not refreshed
- The user's ID is from another organisation with no matching entry
Quick fixes
- Check the Access server and Not access server fields on the Security tab of the Server document
- Confirm the user's group membership, and try a flatter group structure if wildcards are in nested groups
- Refresh the Domino Directory views (or wait for the update task) and have the user retry
- If groups come from a secondary directory, check the Directory Assistance group authorisation settings