Freenas won't connect to Active Directory

[TVo]

I'm using freenas 8.3.0-RELEASE-x64 and I am having a hell of a time getting it to connect to my Active Directory. For some reason it isn't able to reach a KDC in my domain.

I'm using Windows Server 2012 and it's very possible I don't have something configured correctly on that end.

Anyone ever run into anything like this?

Thank

Dec 7 13:57:01 freenas notifier: False
Dec 7 13:57:01 freenas ActiveDirectory: /usr/sbin/service ix-kerberos quietstart
Dec 7 13:57:01 freenas ActiveDirectory: /usr/sbin/service ix-nsswitch quietstart
Dec 7 13:57:01 freenas ActiveDirectory: /usr/sbin/service ix-pam quietstart
Dec 7 13:57:02 freenas ActiveDirectory: /usr/sbin/service ix-kinit quietstart
Dec 7 13:57:02 freenas notifier: kinit: krb5_get_init_creds: unable to reach any KDC in realm MCBADASS

 

[TVo]

Looking at my /etc/krb5.conf I did see that any of the options that mentioned KDC had nothing in them? Should those be populated? Here is a copy of my krb5.conf file:

Code:

[appdefaults]
        pam = {
                forwardable = true
                ticket_lifetime = 36000
                renew_lifetime = 36000
        }

[libdefaults]
        dns_lookup_realm = true
        dns_lookup_kdc = true
        ticket_lifetime = 24h
        clockskew = 300
        forwardable = yes
        default_realm = MCBADASS

[logging]
        default = SYSLOG:INFO:LOCAL7

[realms]
        MCBADASS = {
                kdc = 
                admin_server =
                default_domain = mcbadass
                kpasswd_server =
        }

[domain_realm]
        mcbadass = MCBADASS
        .mcbadass = MCBADASS
        MCBADASS = MCBADASS
        .MCBADASS = MCBADASS

My domain is a local domain called mcbadass. I've tried typing in mcbadass AND mcbadass.local in the Active Directory Config area but it doesn't change anything.

 

[TVo]

Well I'll be damned. I rebooted and it seemed to work. For some reason CIFS service (which was enabled before) was not turned on after the restart. Re-enabled it and then for some reason AD had no problem connecting. Not sure why I had this issue, but I'm glad it's solved!