More and more people are using secure LDAP connection to import users from Active Directory. NxFilter supports this through the LDAPS protocol.
However, we had a problem. We initially tried to simplify the setup by allowing the use of server IP address instead of using domain and certificate, and we made providing the AD domain controller's fully qualified domain name (FQDN) optional.
Unfortunately, this approach stopped working.
We fixed the problem by v4.6.9.1 of NxFilter. Now, you must use an FQDN that matches the domain in your certificate. Also, NxFilter should be able to resolve your server's FQDN. The simplest way to do this is to add an entry for your server's FQDN in the /etc/hosts file on your NxFilter system.
However, we had a problem. We initially tried to simplify the setup by allowing the use of server IP address instead of using domain and certificate, and we made providing the AD domain controller's fully qualified domain name (FQDN) optional.
Unfortunately, this approach stopped working.
We fixed the problem by v4.6.9.1 of NxFilter. Now, you must use an FQDN that matches the domain in your certificate. Also, NxFilter should be able to resolve your server's FQDN. The simplest way to do this is to add an entry for your server's FQDN in the /etc/hosts file on your NxFilter system.