I have already read through a bunch of these threads but nobody's problems seem to be the same as mine. I am hoping mine is relatively easy.
Here is the log file whenever I try to start the AD service, obviously sanitized domain name and username.
On my DC in the Security log I get 3 Audit Success messages stating "Special privileges assigned to new logon." then "An account was successfully logged on." then "An account was logged off."
So it seems as though Freenas is connecting to my DC, my DC is authenticating it, but yet Freenas is telling me Kerberos can't start?
I have gone through the troubleshooting steps under "Directory Services" on doc.freenas a couple of times and made no progress. I actually got so irritated with this the other day that I had to put it down and come back to it. Still no progress this morning so I am coming to all of you for help!
Here is the log file whenever I try to start the AD service, obviously sanitized domain name and username.
Code:
Nov 20 09:51:31 FREENAS ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py stop cifs Nov 20 09:51:32 FREENAS notifier: Stopping dbus. Nov 20 09:51:32 FREENAS avahi-daemon[46802]: Disconnected from D-Bus, exiting. Nov 20 09:51:32 FREENAS notifier: Waiting for PIDS: 46773. Nov 20 09:51:32 FREENAS notifier: dbus not running? (check /var/run/dbus/dbus.pid). Nov 20 09:51:32 FREENAS notifier: Starting dbus. Nov 20 09:51:32 FREENAS notifier: Stopping avahi-daemon. Nov 20 09:51:32 FREENAS notifier: Stopping avahi-daemon. Nov 20 09:51:32 FREENAS notifier: Failed to kill daemon: No such file or directory Nov 20 09:51:32 FREENAS notifier: Starting avahi-daemon. Nov 20 09:51:32 FREENAS avahi-daemon[48469]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Nov 20 09:51:32 FREENAS notifier: winbindd not running? (check /var/run/samba/winbindd.pid). Nov 20 09:51:32 FREENAS notifier: smbd not running? (check /var/run/samba/smbd.pid). Nov 20 09:51:32 FREENAS notifier: nmbd not running? (check /var/run/samba/nmbd.pid). Nov 20 09:51:33 FREENAS ActiveDirectory: /usr/sbin/service ix-kerberos quietstart Nov 20 09:51:33 FREENAS ActiveDirectory: AD_init: config exists, loading values from /etc/directoryservice/ActiveDirectory/config Nov 20 09:51:33 FREENAS ActiveDirectory: generate_krb5_conf: krbhost=S1.mydomain.local, kpwdhost=S1.mydomain.local, domainname=mydomain Nov 20 09:51:33 FREENAS ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart Nov 20 09:51:33 FREENAS ActiveDirectory: /usr/sbin/service ix-pam quietstart Nov 20 09:51:33 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit quietstart Nov 20 09:51:33 FREENAS ActiveDirectory: AD_init: config exists, loading values from /etc/directoryservice/ActiveDirectory/config Nov 20 09:51:33 FREENAS ActiveDirectory: kerberos_start: kinit --password-file=/tmp/tmp.Udh1an7h adminuser@MYDOMAIN Nov 20 09:51:33 FREENAS ActiveDirectory: kerberos_start: Failed Nov 20 09:51:43 FREENAS ActiveDirectory: /usr/sbin/service ix-kinit status Nov 20 09:51:43 FREENAS ActiveDirectory: AD_init: config exists, loading values from /etc/directoryservice/ActiveDirectory/config Nov 20 09:51:43 FREENAS ActiveDirectory: kerberos_status: klist -l | grep -q ^adminuser@MYDOMAIN Nov 20 09:51:43 FREENAS ActiveDirectory: kerberos_status: Failed
On my DC in the Security log I get 3 Audit Success messages stating "Special privileges assigned to new logon." then "An account was successfully logged on." then "An account was logged off."
So it seems as though Freenas is connecting to my DC, my DC is authenticating it, but yet Freenas is telling me Kerberos can't start?
I have gone through the troubleshooting steps under "Directory Services" on doc.freenas a couple of times and made no progress. I actually got so irritated with this the other day that I had to put it down and come back to it. Still no progress this morning so I am coming to all of you for help!