Installed a new Freenas 9.2.1.7 (X64) but I cannot get Active directory integration going. I have got CIFS share working but every time I start Directory services it states "the service could not be started". It looks like DNS is working as well as NTP settings are correct. It will not communicate with my SBS 2011 server no matter what setting I put in!
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
directory services will not start
- Thread starter Benjovy
- Start date
- Status
- Joined
- Mar 6, 2014
- Messages
- 9,554
Version of Windows server? Domain functional level? Are you trying to join it to an existing domain or is this in a testing environment? What messages are being generated in your logs? [/var/log/messages, /var/log/samba4/log.smbd, /var/log/samba4/log.wb-[domain name]
Can you ping your DC by FQDN from your FreeNAS box? Verify that time is correct on the FreeNAS box.
If you have the hardware available I recommend getting AD integration working in a test environment with a minimal AD setup then figuring out configuration differences between your test setup and your production setup. If all else fails, AD indicates you are doing this at a business. It might be a good idea to purchase a support contract.
Can you ping your DC by FQDN from your FreeNAS box? Verify that time is correct on the FreeNAS box.
If you have the hardware available I recommend getting AD integration working in a test environment with a minimal AD setup then figuring out configuration differences between your test setup and your production setup. If all else fails, AD indicates you are doing this at a business. It might be a good idea to purchase a support contract.
2008 r2...domain function level is 2008 and its an existing domain. I can ping FQDN, and NTP settings and time are correct. I have other NAS boxes that are "off the shelf" (Synology) that connect without issue to AD. Setting up a test AD network is a worthless exercise if everything else is connecting to AD except FreeNAS. I have followed a number of forum threads from others that are having the same issue but there is no solution. Looks like FreeNAS has AD integration issues.
Only error I can see is in the log.smb4
Warning The "acl check permissions" option is deprecated
=======================================
/var/log messages (started a new log to get Directory services log info)
Aug 19 13:06:42 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/bin/getent passwd 'TP'
Aug 19 13:06:43 freenas notifier: Performing sanity check on Samba configuration: OK
Aug 19 13:06:43 freenas notifier: Starting nmbd.
Aug 19 13:06:43 freenas notifier: Starting smbd.
Aug 19 13:06:43 freenas nmbd[71355]: [2014/08/19 13:06:43.053682, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 13:06:43 freenas notifier: Starting winbindd.
Aug 19 13:06:43 freenas smbd[71359]: [2014/08/19 13:06:43.096314, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 13:06:43 freenas winbindd[71363]: [2014/08/19 13:06:43.124513, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbi
ndd_cache)
Aug 19 13:06:43 freenas winbindd[71363]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 19 13:06:43 freenas winbindd[71363]: [2014/08/19 13:06:43.126423, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Only error I can see is in the log.smb4
Warning The "acl check permissions" option is deprecated
=======================================
/var/log messages (started a new log to get Directory services log info)
Aug 19 13:06:42 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/bin/getent passwd 'TP'
Aug 19 13:06:43 freenas notifier: Performing sanity check on Samba configuration: OK
Aug 19 13:06:43 freenas notifier: Starting nmbd.
Aug 19 13:06:43 freenas notifier: Starting smbd.
Aug 19 13:06:43 freenas nmbd[71355]: [2014/08/19 13:06:43.053682, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 13:06:43 freenas notifier: Starting winbindd.
Aug 19 13:06:43 freenas smbd[71359]: [2014/08/19 13:06:43.096314, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 13:06:43 freenas winbindd[71363]: [2014/08/19 13:06:43.124513, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbi
ndd_cache)
Aug 19 13:06:43 freenas winbindd[71363]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 19 13:06:43 freenas winbindd[71363]: [2014/08/19 13:06:43.126423, 0] ../lib/util/become_daemon.c:136(daemon_ready)
even tried the step by step bouncing ball http://forums.freenas.org/index.php...directory-folder-file-user-permissions.20610/
- Joined
- Mar 6, 2014
- Messages
- 9,554
What are the results of trying to join the domain manually? (net ads join -S dcname -U administrator)
The following is just based off things remembered from 4 months ago when I set up my FreeNAS as a member server. [Note that 4 months for a parent with small kids is like 4 years for a single person.]
Do you have the Domain Controller's hostname entered under Services -> Directory Services -> Active Directory -> Advanced Mode?
I vaguely recall having to set the default gateway under networking (and thinking 'this doesn't make sense')
The following is just based off things remembered from 4 months ago when I set up my FreeNAS as a member server. [Note that 4 months for a parent with small kids is like 4 years for a single person.]
Do you have the Domain Controller's hostname entered under Services -> Directory Services -> Active Directory -> Advanced Mode?
I vaguely recall having to set the default gateway under networking (and thinking 'this doesn't make sense')
- Status
Similar threads
