Ingo Asche
2022-Nov-20 14:21 UTC
[Samba] No longer access to shares after upgrade to 4.17.3
Hi All, I've just updated my domain from 4.16.6 to 4.17.3 using the bullseye-backports. The update itself worked as smooth as Michael has mentioned. But I have now a problem that seems to be only located on my Windows 10 machines. After login again, I have no longer access to my shares. It seems only be limited to those shares where the rights are set via groups. The home share is not affected as the user has direct rights to it. It's limited also to normal users, if I do the same with an admin user the shares are fully accessible. If I try to mount the same shares from a Linux client it works. Protocol for all is SMB3. As I can't find an obvious error I would much appreciate a hint where I should have a look on... -- Regards Ingo https://github.com/WAdama
Ingo Asche
2022-Nov-20 16:13 UTC
[Samba] No longer access to shares after upgrade to 4.17.3
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. Has anyone an idea what's causing this behaviour? Regards Ingo https://github.com/WAdama Ingo Asche via samba schrieb am 20.11.2022 um 15:21:> Hi All, > > I've just updated my domain from 4.16.6 to 4.17.3 using the > bullseye-backports. > > The update itself worked as smooth as Michael has mentioned. > > But I have now a problem that seems to be only located on my Windows > 10 machines. After login again, I have no longer access to my shares. > > It seems only be limited to those shares where the rights are set via > groups. The home share is not affected as the user has direct rights > to it. It's limited also to normal users, if I do the same with an > admin user the shares are fully accessible. > > If I try to mount the same shares from a Linux client it works. > Protocol for all is SMB3. > > As I can't find an obvious error I would much appreciate a hint where > I should have a look on... >