FreeNAS-8.3.0-BETA3-x64 and Windows Server 2012 AD?

Status
Not open for further replies.

enghausen

Cadet
Joined
Oct 2, 2012
Messages
2
Hallo

I have a setup with a Windows Server 2012 AD in a ESXi 5.1 environment, and a psychical FreeNAS-8.3.0-BETA3-x64 host.

I try to get the Freenas Active Directory Service to talk with my Windows Server 2012 AD - I can se in the Windows log, the freenas host can make a successfully login, buy i get the "the service could not start" from my freenas, the freenas log says this.

Oct 7 18:26:35 nas01 ActiveDirectory: /usr/sbin/service ix-kerberos quietstart
Oct 7 18:26:36 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:36 nas01 ActiveDirectory: generate_krb5_conf: krbhost=, kpwdhost=,$
Oct 7 18:26:36 nas01 ActiveDirectory: generate_krb5_conf: verify_krb5_conf: /r$
Oct 7 18:26:36 nas01 ActiveDirectory: generate_krb5_conf: verify_krb5_conf: /r$
Oct 7 18:26:36 nas01 ActiveDirectory: generate_krb5_conf: verify_krb5_conf: /r$
Oct 7 18:26:36 nas01 ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Oct 7 18:26:36 nas01 ActiveDirectory: /usr/sbin/service ix-pam quietstart
Oct 7 18:26:36 nas01 ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Oct 7 18:26:36 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:36 nas01 ActiveDirectory: kerberos_start: kinit --password-file=/t$
Oct 7 18:26:36 nas01 ActiveDirectory: kerberos_start: Successful
Oct 7 18:26:46 nas01 ActiveDirectory: /usr/sbin/service ix-kinit status
Oct 7 18:26:46 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:46 nas01 ActiveDirectory: kerberos_status: klist -l | grep -q ^eng$
Oct 7 18:26:46 nas01 ActiveDirectory: kerberos_status: Successful
Oct 7 18:26:46 nas01 ActiveDirectory: /usr/sbin/service ix-samba quietstart
Oct 7 18:26:47 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:47 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: checking testparm i$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: Load smb $
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: max_open_$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: rlimit_ma$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: WARNING: $
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: WARNING: $
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: Loaded se$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: ERROR: Th$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: to the de$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: WARNING: $
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: (by defau$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: Server ro$
Oct 7 18:26:47 nas01 ActiveDirectory: generate_smb_config: testparm: Press ent$
Oct 7 18:26:47 nas01 ActiveDirectory: /usr/local/bin/python /usr/local/www/fre$
Oct 7 18:26:48 nas01 notifier: dbus already running? (pid=50753).
Oct 7 18:26:49 nas01 notifier: Starting avahi-daemon.
Oct 7 18:26:49 nas01 notifier: Daemon already running on PID 50778
Oct 7 18:26:49 nas01 notifier: Removing stale Samba tdb files: ...... done
Oct 7 18:26:49 nas01 notifier: Starting nmbd.
Oct 7 18:26:49 nas01 notifier: Starting smbd.
Oct 7 18:26:49 nas01 notifier: Starting winbindd.
Oct 7 18:26:49 nas01 notifier: True
Oct 7 18:26:49 nas01 ActiveDirectory: /usr/sbin/service ix-activedirectory qui$
Oct 7 18:26:49 nas01 ActiveDirectory: AD_init: config exists, loading values f$
Oct 7 18:26:49 nas01 ActiveDirectory: activedirectory_start: trying to join do$
Oct 7 18:26:49 nas01 ActiveDirectory: AD_join_domain: net ads join -U enghausen
Oct 7 18:26:49 nas01 notifier: Failed to join domain: Invalid configuration ("$
Oct 7 18:26:49 nas01 ActiveDirectory: AD_join_domain: Failed

Have anyone made it with a Windows Server 2012, and freenas 8.3?

/Enghausen
 

enghausen

Cadet
Joined
Oct 2, 2012
Messages
2
The failed configuration where the setting under "Workgroup", when i set it to my subdomain "internal", and my domain to internal.domain.com, it all works! :) - I can confirm it works under Windows Server 2012 AD!! :)
 

snaketek

Cadet
Joined
Sep 11, 2012
Messages
1
The failed configuration where the setting under "Workgroup", when i set it to my subdomain "internal", and my domain to internal.domain.com, it all works! :) - I can confirm it works under Windows Server 2012 AD!! :)

I seem to be having the same issue but my knowledge of subdomains is a bit lacking. I am running the same configuration and I am unsure of what the workgroup name should be. If possible, could you elaborate on this?
 
Status
Not open for further replies.
Top