I get the error "..." when I try to get ORF’s AD integration work. How can I fix this?
Article was last updated on October 13, 2020. View products that this article applies to.The following Active Directory-related errors may be logged by ORF:
A referral was returned from the server
Solution: make sure that you have a valid LDAP path configured for ORF (Administration Tool: Blacklists / Recipient Validation, Configure selected). Note that LDAP, GC, DC, ORG, etc. has to be written uppercase and no spaces are allowed between the commas.
The authentication mechanism is unknown
Solution: make sure that you have proper authentication information defined, both the user name and password is correct. Note that your server may require the user name in format DOMAIN\username or username@DOMAIN.
Could not bind to path "..."
Solution: check the LDAP path. Note that LDAP, GC, DC, ORG, etc. has to be written uppercase and no spaces are allowed between the commas.
If the above does not help, try the synchronization with and without authentication (also with authentication with blank user information). ORF AD synchronization queries AD-specific properties, so it also requires the AD schema extension by Microsoft Exchange 2019/2016/2013/2010. Synchronization with a regular Active Directory without these schema extensions is not supported.
Applies To
The article above applies to the following products and versions:
- ORF 6.8.3
- ORF 6.8.2
- ORF 6.8.1
- ORF 6.8
- ORF 6.7
- ORF 6.6.1
- ORF 6.6
- ORF 6.5
- ORF 6.4
- ORF 6.3
- ORF 6.2.1
- ORF 6.2
- ORF 6.1.1
- ORF 6.1
- ORF 6.0.1
- ORF 6.0
- ORF 5.5.1
- ORF 5.5
- ORF 5.4.1
- ORF 5.4
- ORF 5.3
- ORF 5.2
- ORF 5.1
- ORF 5.0