Chris Dill
Contributor
- Joined
- Jan 1, 2014
- Messages
- 116
I have been running this FreeNAS box for almost a year with zero issues. A month ago, I migrated my domain to a new server, a Dell PowerEdge. I put Server 2012 R2 on it.
I started to experience problems keeping CIFS started, and activating AD service. There was a trick I read where I had to change it from AD to Domain Controller and back again. This past week, I lost connection to my ADS when I implimented IPv6. I did IPv6 to utilize DirectAccess through my Windows domain. I attempted to configure dual stack on FreeNAS, finally finding out you can't do it. After this, I could not connect to AD at all.
Since then, I have factory reset, downgraded, upgraded, and tried the beta. I am getting the same errors across all versions, so I do not think it is a bug, but perhaps just a nasty setting.
This past time, I factory reset it, setup basic networking, and tried to join AD- no plugins or anything special. These are the log messages when I try to start AD service:
Those lines at the end are what I have been seeing across versions. I can see the domain:
But I cannot join it:
I can ping both ways, I can ping the gateways, resolve DNS names. If I turn on NFS and share I can access my data. I just cannot join AD. This is giving me other issues, as all of my shares are done over CIFS with windows permissions for various reasons.
As of right now I am on FreeNAS-9.2.1.6-BETA-5c259f3-x64
AMD A4-4000 APU with Radeon(tm) HD Graphics
16 GB of RAM
My load average is LOW.
I have tried to create the AD object manually, I have changed around permissions etc. I have changed around domain GPO to allow communication based on some random post I found about Server 2012 R2. I have tried various Aux Params including:
preferred master = no
domain master = no
realm = DILLDESIGN.LOCAL
security = ads
Any help would be GREAT, I am at my wits end. I would say that I would kill all my jails and start from scratch... except that I have already done this.
I started to experience problems keeping CIFS started, and activating AD service. There was a trick I read where I had to change it from AD to Domain Controller and back again. This past week, I lost connection to my ADS when I implimented IPv6. I did IPv6 to utilize DirectAccess through my Windows domain. I attempted to configure dual stack on FreeNAS, finally finding out you can't do it. After this, I could not connect to AD at all.
Since then, I have factory reset, downgraded, upgraded, and tried the beta. I am getting the same errors across all versions, so I do not think it is a bug, but perhaps just a nasty setting.
This past time, I factory reset it, setup basic networking, and tried to join AD- no plugins or anything special. These are the log messages when I try to start AD service:
Code:
Jun 18 21:31:51 freenas ActiveDirectory: /usr/sbin/service ix-samba start Jun 18 21:31:52 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc' Jun 18 21:31:52 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpO_7boy -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb Jun 18 21:31:52 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap add unixgroup='chrisftp' ntgroup='chrisftp' Jun 18 21:31:52 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap add unixgroup='backupftp' ntgroup='backupftp' Jun 18 21:31:52 freenas ActiveDirectory: /usr/local/bin/python /usr/local/www/freenasUI/middleware/notifier.py start cifs Jun 18 21:31:54 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc' Jun 18 21:31:54 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpLm45w3 -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb Jun 18 21:31:54 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap add unixgroup='chrisftp' ntgroup='chrisftp' Jun 18 21:31:54 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap add unixgroup='backupftp' ntgroup='backupftp' Jun 18 21:31:54 freenas notifier: Performing sanity check on Samba configuration: OK Jun 18 21:31:54 freenas notifier: Starting nmbd. Jun 18 21:31:54 freenas notifier: Starting smbd. Jun 18 21:31:54 freenas nmbd[33981]: [2014/06/18 21:31:54.575548, 0] ../lib/util/become_daemon.c:136(daemon_ready) Jun 18 21:31:54 freenas notifier: Starting winbindd. Jun 18 21:31:54 freenas smbd[33985]: [2014/06/18 21:31:54.648186, 0] ../lib/util/become_daemon.c:136(daemon_ready) Jun 18 21:31:54 freenas winbindd[33991]: [2014/06/18 21:31:54.693355, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache) Jun 18 21:31:54 freenas winbindd[33991]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jun 18 21:31:54 freenas winbindd[33991]: [2014/06/18 21:31:54.696307, 0] ../source3/winbindd/winbindd_util.c:634(init_domain_list) Jun 18 21:31:54 freenas winbindd[33991]: Could not fetch our SID - did we join? Jun 18 21:31:54 freenas winbindd[33991]: [2014/06/18 21:31:54.696400, 0] ../source3/winbindd/winbindd.c:1204(winbindd_register_handlers) Jun 18 21:31:54 freenas winbindd[33991]: unable to initialize domain list
Those lines at the end are what I have been seeing across versions. I can see the domain:
Code:
[root@freenas ~]# net ads info -U Administrator Enter Administrator's password: LDAP server: 192.168.2.254 LDAP server name: DELL.DILLDESIGN.local Realm: DILLDESIGN.LOCAL Bind Path: dc=DILLDESIGN,dc=LOCAL LDAP port: 389 Server time: Wed, 18 Jun 2014 21:44:45 PDT KDC server: 192.168.2.254 Server time offset: -8
But I cannot join it:
Code:
[root@freenas ~]# net ads join -U Administrator Enter Administrator's password: Failed to join domain: failed to lookup DC info for domain 'DILLDESIGN.LOCAL' ov er rpc: NT_STATUS_CONNECTION_RESET
I can ping both ways, I can ping the gateways, resolve DNS names. If I turn on NFS and share I can access my data. I just cannot join AD. This is giving me other issues, as all of my shares are done over CIFS with windows permissions for various reasons.
As of right now I am on FreeNAS-9.2.1.6-BETA-5c259f3-x64
AMD A4-4000 APU with Radeon(tm) HD Graphics
16 GB of RAM
My load average is LOW.
I have tried to create the AD object manually, I have changed around permissions etc. I have changed around domain GPO to allow communication based on some random post I found about Server 2012 R2. I have tried various Aux Params including:
preferred master = no
domain master = no
realm = DILLDESIGN.LOCAL
security = ads
Any help would be GREAT, I am at my wits end. I would say that I would kill all my jails and start from scratch... except that I have already done this.