i've been trying to setup a brand new t12-500 pro, and get it into my local active directory domain with a frustratingly lack of luck
- no data on this array yet, so i went as far as to factory reset it completely this afternoon and then install the latest beta(7.0.0601) immediately to try again
- after factory reset, i did not bond the nics like i had it before (and eventually will need it), 10gb connection, but for simplicity single nic, static ip address
- domain at win2016 level
- join attempts utilizing domain administrator
-- when reviewing logs, particularly syslog, i saw my password in clear text on a lines after where it showed a join attempt encrypted.. (seriously not cool - passwords should never be logged in clear text to log files)
- process always fails with either "NetBIOS Verification Failed" or "SMB workgroup set incorrectly" at the Check domain service step, regardless of what's set in the various fields + what workgroup is set to over under file service
- even tried precreating a domain computer account so it would have something to join as directly in an OU vs. just dumping into cn=Computers
i've got multiple linux and synology boxes in the domain and haven't had any real issues on that front, but this is vexing me - going manual and checking to see if i can get kerberos tickets, other manual samba join type concepts worked from the command line when troubleshooting before i did the factory wipe, but doing that gets nuked by any edits in the UI since it'll clear out and overwrite smb-domain.conf, etc.. i even went as far as force enabling SMB1 at the domain level (cause who needs security, goes well with the clear text pw) without any luck.
i still feel like i'm missing something obvious here, so if i am, please feel free to point out and chastise appropriately, but i just want this to work before i move anything over to it
any ideas?
EDIT: just a followup, i hard reset the unit again and was able to join the domain just fine from TOS6, and that domain registration carried over with an upgrade (and subsequent update) just fine - it seems to be something in whatever changed with that process for TOS7 from scratch.
EDIT EDIT: ok i lied, even though it says "connected" in green still when you go into control panel|domain/ldap - it isn't talking to the domain anymore, seems to have reverted the smb-ads.conf to a default of:
security = ads
kerberos method = secrets and keytab
realm = NOONTEC.NET
template shell = /sbin/nologin
template homedir = /home/%D/%U
winbind offline logon = true
winbind request timeout = 10
winbind enum users = Yes
winbind enum groups = Yes
winbind refresh tickets = yes
winbind separator = \\
idmap config * : backend = autorid
idmap config * : range = 1000000-1999999
log file = /var/log/samba/%m.log
log level = 1
workgroup = WORKGROUP
.. attempting any changes from the UI doesn't stick. That being said, upon further monkeying with it, it seems to be a problem if the nics are 802.3ad bonded, break the bond, it reverts back to talking to the domain again... active/backup bonding seems to work though, but that doesn't really get me the 20gb uplink i was hoping for. It does seem that when you have bonding enabled at all, the UI shows a "No valid data" in the "Register DNS Interface" under advanced in the Domain/LDAP section