Couldn't connect to active directory

[steini]

Hello all,

we have a FreeNAS 9.2.1.9 that running fine. Now I've made a test installation with the new version 9.3. Unfotunalety is isn't possible to join to our w2k3 domain. I can't find the mistake. I've extracted some lines from the /var/log/debug.log file. You can find it in the attached file 2014-12-11_debug-log.txt. Than I run the directory start script (/etc/directoryservice/ActiveDirectory/ctl start). It failed. I've attached it - 2014-12-11_directory_start.txt. What is the cause that the binding to the active directory fails?

Domain functional level: Windows Server 2003

[root@freenas] ~# host -t srv _ldap._tcp.msdev.intern.testing.de
_ldap._tcp.msdev.intern.testing.de has SRV record 0 100 389 win2k3ad-mirror.msdev.intern.testing.de.
_ldap._tcp.msdev.intern.testing.de has SRV record 0 100 389 win2k3ad.msdev.intern.testing.de.
_ldap._tcp.msdev.intern.testing.de has SRV record 0 100 389 backupdc.msdev.intern.testing.de.

Ping is possible in both directions.

Thanks in advance
steini

 

[dlavigne]

Is https://bugs.freenas.org/issues/7080#note-1 applicable? If binding isn't the issue, what is the idmap backend set to?

 

[steini]

The freeNAS 9.3 instance isn't an upgrade. Thats a completely new installation. But i'm not sure whether ssl/tls is in use. With the ldp.exe tool and I could connect via ssl to the server. The idmap backend is set to adex. But I tried it with various possibilities.

 

[dlavigne]

rid is the default and should work, unless the environment is using something different. See Table 9.1a at
http://doc.freenas.org/9.3/freenas_directoryservice.html?highlight=idmap#active-directory.

 

[steini]

Unfortunately also with rid wasn't able to start the service.

 

[dlavigne]

There's been some recent AD bugs since RELEASE: https://bugs.freenas.org/projects/freenas/activity. If none of those seem to apply and you can't figure out the underlying issue (or get help here), please create a bug report that also includes your smb4.conf and post the issue number here.