[Samba] No longer access to shares after upgrade to 4.17.3

Ingo Asche foren at asche-rz.de
Mon Nov 21 10:37:12 UTC 2022

Just for documentation: The one login with admin rights doesn't change 
anything. It seems it's only the for the runtime of the token on the 
server I presume.


Ingo Asche via samba schrieb am 20.11.2022 um 17:43:
> Hi Michael,
> thanks for the input.
> Forgot to mention it: The shares are located on a Synology NAS joined 
> to my little domain. So there has nothing changed, but to be sure I've 
> checked it. I have just once to logon to Windows with full rights and 
> after this it works again with normal rights. I even don't have to 
> open the shares for this this.
> And - as mentioned in my first mail - this only happens on my Windows 
> clients. A mount from a Linux client works without such doing.
> Regards
> Ingo
> https://github.com/WAdama
> Michael Tokarev via samba schrieb am 20.11.2022 um 17:27:
>> 20.11.2022 19:13, Ingo Asche via samba wrote:
>>> Just found out something funny:
>>> If I give the affected user the rights of Domain Admins, then - of 
>>> course - the share mapping works. Then I logoff and delete the group 
>>> from the user. After logging in again, the shares are mapped and 
>>> again accessible as before the update with the given rights.
>> I don't have an idea, but I do have a general suggestion.
>> How does your samba map ACLs?
>> Take a look at the differences between file ACLs before
>> and after. This should give some clues.
>> Thanks,
>> /mjt

More information about the samba mailing list