Can't get FreeNAS to sync with Active Directory

Status
Not open for further replies.
T

Tal Girhish

Cadet
Joined
Aug 18, 2014
Messages
9
Hi guys,
I'm very hopeless..
I've searched the whole web and I couldn't find any post that had the same problem like I have.
Can't get FreeNAS to sync with my domain-controller.

I've also tried this thread and it wasn't helpful

I'm running a 2008R2/2003 mixed domain, and the FreeNAS runs on an ESXi host.
I've followed all of the steps that in the 9.2.1 Users Guide :
  • pinged the domain name of the Active Directory domain controller from Shell on the FreeNAS
  • Updated DNS server and default gateway settings in Network → Global
    Configuration
  • Added a DNS record for the FreeNAS system on the Windows server and verify that I can ping
    the hostname of the FreeNAS system from the domain controller
  • configured an NTP Server (My PDC)
  • And also configured the Services → Directory Services → Active Directory properly.
I first thought that i messed things out and then I've created another FreeNAS server,
but after some research on the web I'm starting to think about problems with my DNS server or Kerberos.
Although i must say that my entire network works great with my current DNS and DC server,
And I also run "DCDIAG" to monitor problems and i didn't found any.
I tried to sync FreeNAS with the first DC and with the second one with configuring it at the "Advanced" tab under the Directory Services configuration screen and it also didn't work.

I get at the top of the screen "The service could not be started"

Details :
* FreeNAS version: 9.2.1
* 16GB RAM
*Domain functional level - 2003
The following is from the latest freenas i've installed:
Code:
Aug 19 15:06:23 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py stop cifs
Aug 19 15:06:23 FREENAS notifier: Stopping winbindd.
Aug 19 15:06:23 FREENAS winbindd[15665]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=1)
Aug 19 15:06:23 FREENAS winbindd[15666]: [2014/08/19 15:06:23.878419,  0] ../source3/winbindd/winbindd.c:234(winbindd_sig_term_handler)
Aug 19 15:06:23 FREENAS winbindd[15666]:   Got sig[15] terminate (is_parent=0)
Aug 19 15:06:23 FREENAS notifier: Waiting for PIDS: 15665.
Aug 19 15:06:23 FREENAS notifier: Stopping smbd.
Aug 19 15:06:23 FREENAS notifier: Waiting for PIDS: 15661.
Aug 19 15:06:23 FREENAS notifier: Stopping nmbd.
Aug 19 15:06:23 FREENAS nmbd[15657]: [2014/08/19 15:06:23.887207,  0] ../source3/nmbd/nmbd.c:57(terminate)
Aug 19 15:06:23 FREENAS nmbd[15657]:   Got SIGTERM: going down...
Aug 19 15:06:23 FREENAS notifier: Waiting for PIDS: 15657.
Aug 19 15:06:23 FREENAS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart
Aug 19 15:06:24 FREENAS ix-kerberos: generate_krb5_conf: krbhost=dc-pituah.pituah.iaf,  kpwdhost=dc-pituah.pituah.iaf, domainname=pituah.iaf
Aug 19 15:06:24 FREENAS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Aug 19 15:06:24 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Aug 19 15:06:36 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit status
Aug 19 15:06:37 FREENAS ActiveDirectory: /usr/sbin/service ix-samba quietstart
Aug 19 15:06:38 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:06:38 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpZNJJF7 -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:06:38 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:06:38 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py start cifs
Aug 19 15:06:39 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:06:40 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpqfQCP5 -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:06:40 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:06:40 FREENAS notifier: Performing sanity check on Samba configuration: OK
Aug 19 15:06:40 FREENAS notifier: Starting nmbd.
Aug 19 15:06:40 FREENAS notifier: Starting smbd.
Aug 19 15:06:40 FREENAS nmbd[19164]: [2014/08/19 15:06:40.414330,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:06:40 FREENAS nmbd[19164]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connectionssend_host_announcement: type 809b03 for host FREENAS on subnet 192.168.108.10 for workgroup PITUAH.IAF
Aug 19 15:06:40 FREENAS notifier: Starting winbindd.
Aug 19 15:06:40 FREENAS smbd[19168]: [2014/08/19 15:06:40.473203,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:06:40 FREENAS smbd[19168]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionswaiting for connections
Aug 19 15:06:40 FREENAS winbindd[19172]: [2014/08/19 15:06:40.517408,  0] ../source3/winbindd/winbindd_util.c:634(init_domain_list)
Aug 19 15:06:40 FREENAS winbindd[19172]:   Could not fetch our SID - did we join?
Aug 19 15:06:40 FREENAS winbindd[19172]: [2014/08/19 15:06:40.517761,  0] ../source3/winbindd/winbindd.c:1204(winbindd_register_handlers)
Aug 19 15:06:40 FREENAS winbindd[19172]:   unable to initialize domain list
Aug 19 15:06:40 FREENAS ActiveDirectory: /usr/sbin/service ix-activedirectory quietstart
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.431999,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:06:42 FREENAS nmbd[19164]:   my_name_register_failed: Failed to register my name FREENAS<20> on subnet 192.168.108.10.
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.432142,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:06:42 FREENAS nmbd[19164]:   standard_fail_register: Failed to register/refresh name FREENAS<20> on subnet 192.168.108.10
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.432201,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:06:42 FREENAS nmbd[19164]:   my_name_register_failed: Failed to register my name FREENAS<03> on subnet 192.168.108.10.
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.432253,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:06:42 FREENAS nmbd[19164]:   standard_fail_register: Failed to register/refresh name FREENAS<03> on subnet 192.168.108.10
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.432303,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:06:42 FREENAS nmbd[19164]:   my_name_register_failed: Failed to register my name FREENAS<00> on subnet 192.168.108.10.
Aug 19 15:06:42 FREENAS nmbd[19164]: [2014/08/19 15:06:42.432352,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:06:42 FREENAS nmbd[19164]:   standard_fail_register: Failed to register/refresh name FREENAS<00> on subnet 192.168.108.10
Aug 19 15:06:51 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py stop cifs
Aug 19 15:06:52 FREENAS notifier: winbindd not running? (check /var/run/samba/winbindd.pid).
Aug 19 15:06:52 FREENAS notifier: Stopping smbd.
Aug 19 15:06:52 FREENAS notifier: Waiting for PIDS: 19168.
Aug 19 15:06:52 FREENAS notifier: Stopping nmbd.
Aug 19 15:06:52 FREENAS nmbd[19164]: [2014/08/19 15:06:52.404142,  0] ../source3/nmbd/nmbd.c:57(terminate)
Aug 19 15:06:52 FREENAS nmbd[19164]:   Got SIGTERM: going down...
Aug 19 15:06:52 FREENAS notifier: Waiting for PIDS: 19164.
Aug 19 15:06:52 FREENAS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Aug 19 15:06:52 FREENAS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Aug 19 15:06:52 FREENAS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Aug 19 15:06:52 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Aug 19 15:06:52 FREENAS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Aug 19 15:06:54 FREENAS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Aug 19 15:06:55 FREENAS ActiveDirectory: /usr/sbin/service samba_server forcestop
Aug 19 15:06:55 FREENAS ActiveDirectory: /usr/sbin/service ix-samba start
Aug 19 15:06:56 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:06:56 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpxOGz8j -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:06:56 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:06:56 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py start cifs
Aug 19 15:06:57 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:06:57 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpxYHNRw -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:06:57 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:06:57 FREENAS notifier: Performing sanity check on Samba configuration: OK
Aug 19 15:06:57 FREENAS notifier: Starting nmbd.
Aug 19 15:06:57 FREENAS notifier: Starting smbd.
Aug 19 15:06:57 FREENAS nmbd[21556]: [2014/08/19 15:06:57.930537,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:06:57 FREENAS nmbd[21556]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connectionssend_host_announcement: type 819a03 for host FREENAS on subnet 192.168.108.10 for workgroup PITUAH.IAF
Aug 19 15:06:57 FREENAS notifier: Starting winbindd.
Aug 19 15:06:57 FREENAS smbd[21560]: [2014/08/19 15:06:57.984932,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:06:57 FREENAS smbd[21560]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionswaiting for connections
Aug 19 15:06:58 FREENAS winbindd[21566]: [2014/08/19 15:06:58.021395,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Aug 19 15:06:58 FREENAS winbindd[21566]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 19 15:06:58 FREENAS winbindd[21566]: [2014/08/19 15:06:58.024433,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:06:58 FREENAS winbindd[21567]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections[21566]: list trusted domains
Aug 19 15:06:58 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py stop cifs
Aug 19 15:06:59 FREENAS notifier: Stopping winbindd.
Aug 19 15:06:59 FREENAS winbindd[21566]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=1)
Aug 19 15:06:59 FREENAS winbindd[21567]: [2014/08/19 15:06:59.596753,  0] ../source3/winbindd/winbindd.c:234(winbindd_sig_term_handler)
Aug 19 15:06:59 FREENAS winbindd[21567]:   Got sig[15] terminate (is_parent=0)
Aug 19 15:06:59 FREENAS notifier: Waiting for PIDS: 21566.
Aug 19 15:06:59 FREENAS notifier: Stopping smbd.
Aug 19 15:06:59 FREENAS notifier: Waiting for PIDS: 21560.
Aug 19 15:06:59 FREENAS notifier: Stopping nmbd.
Aug 19 15:06:59 FREENAS nmbd[21556]: [2014/08/19 15:06:59.604905,  0] ../source3/nmbd/nmbd.c:57(terminate)
Aug 19 15:06:59 FREENAS nmbd[21556]:   Got SIGTERM: going down...
Aug 19 15:06:59 FREENAS notifier: Waiting for PIDS: 21556.
Aug 19 15:06:59 FREENAS ActiveDirectory: /usr/sbin/service ix-kerberos quietstop
Aug 19 15:06:59 FREENAS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstop
Aug 19 15:06:59 FREENAS ActiveDirectory: /usr/sbin/service ix-pam quietstop
Aug 19 15:06:59 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit forcestop
Aug 19 15:06:59 FREENAS ActiveDirectory: /usr/sbin/service ix-activedirectory forcestop
Aug 19 15:07:01 FREENAS ActiveDirectory: /usr/sbin/service ix-cache quietstop &
Aug 19 15:07:02 FREENAS ActiveDirectory: /usr/sbin/service samba_server forcestop
Aug 19 15:07:02 FREENAS ActiveDirectory: /usr/sbin/service ix-samba start
Aug 19 15:07:03 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:07:03 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpZ_6j6T -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:07:03 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:07:03 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py start cifs
Aug 19 15:07:04 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 19 15:07:04 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmp38qxBd -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 19 15:07:04 FREENAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap list
Aug 19 15:07:04 FREENAS notifier: Performing sanity check on Samba configuration: OK
Aug 19 15:07:04 FREENAS notifier: Starting nmbd.
Aug 19 15:07:04 FREENAS notifier: Starting smbd.
Aug 19 15:07:04 FREENAS nmbd[23312]: [2014/08/19 15:07:04.969282,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:07:04 FREENAS nmbd[23312]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connectionssend_host_announcement: type 819a03 for host FREENAS on subnet 192.168.108.10 for workgroup PITUAH.IAF
Aug 19 15:07:05 FREENAS notifier: Starting winbindd.
Aug 19 15:07:05 FREENAS smbd[23316]: [2014/08/19 15:07:05.025069,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:07:05 FREENAS smbd[23316]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionswaiting for connections
Aug 19 15:07:05 FREENAS winbindd[23320]: [2014/08/19 15:07:05.061265,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Aug 19 15:07:05 FREENAS winbindd[23320]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Aug 19 15:07:05 FREENAS winbindd[23320]: [2014/08/19 15:07:05.064353,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Aug 19 15:07:05 FREENAS winbindd[23321]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connections[23320]: list trusted domains
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.991961,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:07:06 FREENAS nmbd[23312]:   my_name_register_failed: Failed to register my name FREENAS<20> on subnet 192.168.108.10.
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.992083,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:07:06 FREENAS nmbd[23312]:   standard_fail_register: Failed to register/refresh name FREENAS<20> on subnet 192.168.108.10
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.992140,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:07:06 FREENAS nmbd[23312]:   my_name_register_failed: Failed to register my name FREENAS<03> on subnet 192.168.108.10.
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.992193,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:07:06 FREENAS nmbd[23312]:   standard_fail_register: Failed to register/refresh name FREENAS<03> on subnet 192.168.108.10
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.992244,  0] ../source3/nmbd/nmbd_mynames.c:36(my_name_register_failed)
Aug 19 15:07:06 FREENAS nmbd[23312]:   my_name_register_failed: Failed to register my name FREENAS<00> on subnet 192.168.108.10.
Aug 19 15:07:06 FREENAS nmbd[23312]: [2014/08/19 15:07:06.992295,  0] ../source3/nmbd/nmbd_namelistdb.c:320(standard_fail_register)
Aug 19 15:07:06 FREENAS nmbd[23312]:   standard_fail_register: Failed to register/refresh name FREENAS<00> on subnet 192.168.108.10


What am I doing wrong?!
As to the FreeNAS guide, Connecting FreeNAS to Active Directory should be very simple action.
That's why I'm so frustrated,
Please help me!!!
 
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Tal Girhish said:
Yes I'm using a Domain Admin account to join the domain and my hostname is "FreeNAS".
Click to expand...
Being a parent of small children I tend to forget things that happened more than a week ago. This means I can't remember the exact steps I did / problems encountered in the domain join. I can tell you how things are currently set on my server.

System --> System Information
  • Hostname = FreeNAS.foo.com
Services -->Directory Services --> Active Directory
  • Domain Name = foo.com
  • NetBIOS Name = FreeNAS
  • Workgroup Name = foo
  • Domain Account Name = [Domain Admin Account]
  • Under the "Advanced" parameters I have "Domain Controller" = Hostname of my DC. "Use Default Domains" is checked.
Services --> CIFS
  • NetBIOS name = FreeNAS
  • Workgroup = foo
  • Server maximum protocol = SMB2_24

System --> NTP Servers = IP Address of DC

Network --> Network Summary shows the following:
  • Nameserver = IP Address of DC
  • Default route = IP Address of router
 
Last edited:
T

Tal Girhish

Cadet
Joined
Aug 18, 2014
Messages
9
anodos said:
Being a parent of small children I tend to forget things that happened more than a week ago. This means I can't remember the exact steps I did / problems encountered in the domain join. I can tell you how things are currently set on my server.

System --> System Information
  • Hostname = FreeNAS.foo.com
Services -->Directory Services --> Active Directory
  • Domain Name = foo.com
  • NetBIOS Name = FreeNAS
  • Workgroup Name = foo
  • Domain Account Name = [Domain Admin Account]
Services --> CIFS
  • NetBIOS name = FreeNAS
  • Workgroup = foo
  • Server maximum protocol = SMB2_24

System --> NTP Servers = IP Address of DC

Network --> Network Summary shows the following:
  • Nameserver = IP Address of DC
  • Default route = IP Address of router
Click to expand...

Thanks for your reply again,
I think that my problem is not in my FreeNAS configuration,
I think it's DNS or A/D problem.. I also tried to point FreeNAS to communicate with my other DC (2008R2)
and the same problem still accurs.
 
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Tal Girhish said:
Thanks for your reply again,
I think that my problem is not in my FreeNAS configuration,
I think it's DNS or A/D problem.. I also tried to point FreeNAS to communicate with my other DC (2008R2)
and the same problem still accurs.
Click to expand...
If you have the hardware available, you may want to set up a testing environment (on a separate network) with a fresh install of Windows Server and a basic / fresh AD setup. See if you can join the test domain. If it works, then figure out the configuration differences between the two domains.
 
T

Tal Girhish

Cadet
Joined
Aug 18, 2014
Messages
9
I've installed the secondary domain controller just for the reason you just said, but it was in the same environment.

Today I've also installed a new server with latest FreeNAS on it and it didn't work.
The same error occur when I tried connecting it to A/D.

I'll try to join my new FreeNAS server on a different network as you said, thanks.
 
V

Vpluar

Cadet
Joined
Sep 5, 2014
Messages
6
Hello,
I am experiencing a similar problem, I have set up all the enviroment like the 9.2.1 user guide shows but I can't get the domain sync. We are using 2012 DC with the latest version of freenas 9.2.1.7. I have test with wbinfo and it seems that the config I set into the web is not aplying to freenas.

[root@freenas ~]# wbinfo -t
checking the trust secret for domain WORKGROUP via RPC calls failed
error code was NT_STATUS_NO_SUCH_DOMAIN (0xc00000df)
failed to call wbcCheckTrustCredentials: WBC_ERR_AUTH_ERROR
Could not check secret

Another think is that, if I remember right, it should be a service name directory services and it has dissapear. Could it be a bug of the new release?
 

Attachments

  • freenas domain problem.jpg
    freenas domain problem.jpg
    87.6 KB · Views: 335
anodos

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Vpluar said:
[root@freenas ~]# wbinfo -t
checking the trust secret for domain WORKGROUP via RPC calls failed
error code was NT_STATUS_NO_SUCH_DOMAIN (0xc00000df)
failed to call wbcCheckTrustCredentials: WBC_ERR_AUTH_ERROR
Could not check secret
Click to expand...
Please verify that your CIFS config [under services --> CIFS] contains the proper workgroup name. In your case it should be "emartinez".
 
T

Tal Girhish

Cadet
Joined
Aug 18, 2014
Messages
9
anodos said:
If you have the hardware available, you may want to set up a testing environment (on a separate network) with a fresh install of Windows Server and a basic / fresh AD setup. See if you can join the test domain. If it works, then figure out the configuration differences between the two domains.
Click to expand...


OK,

So i setup the following domain on my vmware workstation:

  • I've created a virtual network for those VM's
    • Address 192.168.108.0-255 (Class C)
    • Default Gateway: 192.168.108.1
  • Windows server 2003R2 x64 (Roles: A/D, DHCP, DNS)
    • IP: 192.168.108.100
    • Hostname: DC
    • Domain: Dev.com
    • DC FQDN name: DC.Dev.com
  • FreeNAS 9.2.1.7 x64
    • IP: 192.168.108.16
    • Hostname: freenas
    • Domain: test.com
    • IPv4 Default Gateway: 192.168.108.1
    • Nameserver 1: 192.168.108.100
Network Summary on FreeNAS :
Name IPv4 Address
em0 192.168.108.16/24
Nameserver
192.168.108.100
Default route
192.168.108.1​
  • Windows 8.1 workstation

I setup all the DHCP preferences right, and DNS as well,

Activated the DHCP Scope,

And confirmed the all is good by joining the workstation to the domain successfully.

Next I’ve created a DNS record for freenas (Checked the PTR record too), even gave permission to the DNS record that iv'e created to the user I tried to connect with.

pinged from the freenas shell to DC and back and all was good.

Then again - The service could not be started.
 
V

Vpluar

Cadet
Joined
Sep 5, 2014
Messages
6
I have set emartinez as group in the CIFPS config but with the same result:

[root@freenas ~]# wbinfo -t
checking the trust secret for domain EMARTINEZ via RPC calls failed
error code was NT_STATUS_NO_SUCH_DOMAIN (0xc00000df)
failed to call wbcCheckTrustCredentials: WBC_ERR_AUTH_ERROR
Could not check secret
[root@freenas ~]#

[root@freenas ~]# net ads join -S dc01 -U administrador
Host is not configured as a member server.
Invalid configuration. Exiting....
Failed to join domain: This operation is only allowed for the PDC of the domain.
[root@freenas ~]#
 
T

Thomymaster

Contributor
Joined
Apr 26, 2013
Messages
142
Hi

I just struggled with getting my 9.2.1.6 to work with my Windows SBS 2011 (which is 2008R2) DC (https://bugs.freenas.org/issues/5181).

Can you verify that your DNS config is working, so that these 2 SRV records exist:

_ldap._tcp.dc._msdcs.<domain>
_kerberos._udp.<domain>

then test with (under Windows):
nslookup
set type=srv
_ldap._tcp.dc._msdcs.<domain>

After that i restarted the directory services under FreeNAS "services" and could see that i got a kerberos ticket via:

Code:
[root@freenas-test] ~# klist
Credentials cache: FILE:/tmp/krb5cc_0
        Principal: KuK-Admin@KUK.LOCAL

  Issued           Expires          Principal
Jun 10 22:12:44  Jun 11 08:12:44  krbtgt/KUK.LOCAL@KUK.LOCAL
Jun 10 22:13:07  Jun 11 08:12:44  cifs/filer.KuK.local@KUK.LOCAL
Jun 10 22:13:08  Jun 11 08:12:44  ldap/filer.kuk.local@KUK.LOCAL


then i checked with:

wbinfo -t (check domain trust)
wbinfo -u (lists domain users)
wbinfo -g (lists domain groups)

Hope that helps maybe :)
 
V

Vpluar

Cadet
Joined
Sep 5, 2014
Messages
6
I have checked the DNS entry in my DNS server and both are there. I have check the correct resolution of the names.

Same output from me:
[root@freenas ~]# klist
klist: No ticket file: /tmp/krb5cc_0

where Thomymaster said "After that i restarted the directory services under FreeNAS "services"" you mean that you have a tab in the web freenas portal under the tag service - Control service, do you have a button to set the service directory on or off? like cifps or any other service in the image?
 

Attachments

  • freenas control service.jpg
    freenas control service.jpg
    65.2 KB · Views: 318
V

Vpluar

Cadet
Joined
Sep 5, 2014
Messages
6
Here it is,
can you confirm if in 9.2.1.7 should appear the directory services in the control service tab?

It is to confirm if I have a problem with the installation of freebsd.
 

Attachments

  • smb4.conf.txt
    6.7 KB · Views: 326
Status
Not open for further replies.

Similar threads

F
  • Locked
messages in console
Replies
1
Views
2K
wetpaint
W
esamett
  • Locked
"Broke" my Freenas 9.2.1.6: unable to start CIFS
Replies
7
Views
2K
esamett
esamett
tmacka88
  • Locked
SMB share not working?
Replies
6
Views
2K
tmacka88
tmacka88
S
  • Locked
Freenas, +AD on Windows server 2008
Replies
2
Views
1K
skynet59
S
T
  • Locked
Strange AD Issues on 9.3
Replies
12
Views
2K
sapwood
S
Top