I have an issue I can’t seem to resolve. I’m running Debian 10 Samba server with Windows 10 mapped to Samba share. Local User: bobby. Local Group: bobby. Samba share [bobby$], path = /mnt2/Users/bobby, browseable = yes, read only = no, writeable = yes. Directory: /mnt2/Users/bobby – Owner: root:bobby – Permissions: 2770. For some reason Windows access to mapped share stopped working for group bobby. If I change Directory Owner to root:users Windows access is restored. When I switch back Owner to root:bobby Windows access is again denied. I have deleted and recreated bobby user and group. I have rebooted server and workstation. I have deleted and recreated the directory bobby on the server. All with no success. I can however create a new directory and share with Owner: root:bobby – Permissions: 2770 and all works. It seems something on the server side is stuck in relation to the original directory group ownership.

I’d appreciate any suggestions, answers or clues about how to resolve this issue?

Thank you

As far as I know there is no practical meaning to setting the suid bit on a directory. suid allows a program to run with the privileges of the owner regardless of who launches it.

I had the same problem that my user could not create files the first time I tried recreating your directory but the second time it worked so not sure if it was me or something else. Are you testing this from Windows or on the linux system?

Look at the file server logs on the Windows side.