samba - Mar 2021 - Secondary Unix Groups

Christof,
	Thank you.  Yes.  Winbind is running on this server.  I should have mentioned
that.
 
Sam Liston (sam.liston at utah.edu)
=========================================Center for High Performance Computing -
Univ. of Utah
155 S. 1452 E. Rm 405
Salt Lake City, Utah 84112 (801)232-6932
=========================================

> On Mar 9, 2021, at 4:44 PM, Christof Schmitt <cs at samba.org> wrote:
> 
> On Tue, Mar 09, 2021 at 10:43:47PM +0000, Samuel Taylor Liston via samba
wrote:
>> global.smb.conf
>> [global]
>>        workgroup = AD
>>        server string = CottonWood (%L) Server
>> 	netbios name = chpcvip01
>>        security = ADS
> 
> Just a guess, but since this is an upgrade from Samba 4.7, there is this
> change in Samba 4.8:
> 
> https://www.samba.org/samba/history/samba-4.8.0.html
> 
>    Domain member setups require winbindd
>    -------------------------------------
> 
>    Setups with "security = domain" or "security = ads"
require a
>    running 'winbindd' now. The fallback that smbd directly contacts
>    domain controllers is gone.
> 
> Is winbindd running on the system?
> 
> Christof

On 10/03/2021 01:33, Samuel Taylor Liston wrote:
> Christof,
> 	Thank you.  Yes.  Winbind is running on this server.  I should have
mentioned that.

Winbind might be running, but you are not using it, you need to remove 
sssd, but this may be where your troubles start unless you have been 
using uidNumber & gidNumber attributes in AD.

 From Samba 4.8.0 you can only use sssd for authentication, if you want 
shares, you must use winbind and this means you cannot use sssd.

Rowland