Univention Bugzilla – Bug 43253
FreeNAS and Linux enter the domain but can not recover users
Last modified: 2017-09-15 14:06:31 CEST
Created attachment 8325 [details] log.winbindd in the Endian/FreeNAS After configuring version 4.1-4 of FreeNAS and Endian Firewall (as well as other Linux), I am able to add them to the domain without any errors, but they can not synchronize the users. Windows 10 can successfully log in to the domain. The Domain Controller is Univention 4.1-4 and only has the Administrator as the user.
I made the installation of 4.1-3 and this bug does not exist, both FreeNAS and Endian Firewall can recover users correctly, either using the interface or wbinfo -u/-g. Apparently there may be some bug in the samba packages present in the repository.
Thanks for the report. Can you provide Samba logfiles with debug level 12? ucr set samba/debug/level=12 /etc/init.d/samba restart After trying to synchronize the users, please add /var/log/samba/log.*
Sorry for the delay to respond, I had to set up the environment again because I deleted the VM after the tests went wrong to install 4.1-3. Just to warn you what was done, I installed from the official ISO and selected the option to update the system after completing the configuration of the domain. Upon completion of the process, Univention is in version 4.1-4. With this I applied the commands: ucr set samba/ldap/server/require/strong/auth=no ucr set samba/debug/level=12 And finally I added FreeNAS to the domain. After adding I tried again to use the user list command: kinit Administrator@SAMUR.LOCAL wbinfo -u And no obitive success. The complete Univention Samba log directory is attached. https://drive.google.com/file/d/0Bzo3LmoiOqu_QVRMbHgteEN1dUE/view?usp=sharing Sincerely, Tácio Andrade.
* And I did not succeed. Sorry for the above error.
Thanks. @Felix, please have a look. Michael said that he have a FreeNAS 9.10 test VM.
After updating the latest packages from early 2017 and re-testing, the bug has been resolved. If you could close, thank you, because I do not know this tool very well.
(In reply to Tácio Andrade from comment #6) > After updating the latest packages from early 2017 and re-testing, the bug > has been resolved. > If you could close, thank you, because I do not know this tool very well. Thank you, i close the bug as "worksforme"
Set status of old resolved issues to closed.