When I run samba-gpupdate --force for the first time, the following two lines are problematic/not working for login. winbind separator = \ winbind use default domain = Yes If I manually update to "winbind separator = \\" (which is already set in active directory), I can login with domain\username, but not just username even though winbind use default domain = Yes is set. If I run samba-gpupdate --force again, the two lines look like the following: winbind separator = winbind use default domain = Yes winbind use default domain = No Now I can login only with domainwusername and not just username Again, if I manually update smb.conf I can login but only with domain\username
Is this the same as https://bugzilla.samba.org/show_bug.cgi?id=15768 ?
(In reply to Douglas Bagnall from comment #1) > Is this the same as https://bugzilla.samba.org/show_bug.cgi?id=15768 ? or, rather, the second comment thereof.
email thread: https://lists.samba.org/archive/samba-technical/2024-February/138727.html in which source3/loadparm gets blamed.
It is similar to the other issue, but I really want it to work with default domain setting to Yes which is not working even when set.
(In reply to Jeremy Tucker from comment #4) Where are you setting these parameters: winbind separator = \ winbind use default domain = Yes In a Samba AD DCs smb.conf or in a Unix domain members smb.conf ? They only work on a Unix domain member, they have never worked on a DC, it is one of the reasons why you shouldn't use a DC as a fileserver.
I am making these settings on a Windows Domain Controller in Group Policy. I'm doing samba-gpupdate --force to get the new parameters from the dc, so this is in the domain member's smb.conf where the parameters aren't working.
This is a bug in the way the s4 loadparam dumps the 'winbind separator' parameter. This group policy extension applies smb.conf parameters by loading the existing parameters via loadparam, then setting the new settings, and dumping that content to the smb.conf. The s4 loadparam does a really poor job at jump the parameters, it seems. At least I *think* it's the s4 lp. It's whatever lp is in the py `SambaOptions`.
Second problem is that lp.dump() apparently is ignoring the `show_defaults` parameter. The smb.conf gp extension sets that flag to `false`, but `dump` still dumps the default parameters anyway.