New user cannot access Samba share

[ajbrehm]

I have a few existing users that are members of a group "publicrw" which grants rw access to a Samba share called "public". That works.

Now I created a new user "public", member of "public" with "public" having ro access to the same share. But when I connect as "public" from Windows, I cannot see any files.

When I added the user "public" to the group "publicrw" and rebooted the Windows client and connected to the share again, the drive remains empty.

What am I overlooking?

 

[chuck32]

What am I overlooking?

Hard to tell without screenshots of your settings.

Did you apply permissions recursively?

 

[ajbrehm]

Hard to tell without screenshots of your settings.

Did you apply permissions recursively?

It appears to be the name...

The share also allows everyone@ read access and it works for another new user "haddock".

Oddly enough Windows seems to be a bit weird about user names. While Windows accepts a user name "public" (and then TrueNAS does not), Windows does not accept a user name "test" (complains about guest access not being allowed) or a user name "legrand" (which it also considers guest access).

TrueNAS refuses: public
Windows refuses: test, legrand
Works: haddock, benoit

Maybe Samba has a thing with the name "public" or with a user name that is equal to the share name?

 

[ajbrehm]

I found this older post: https://www.truenas.com/community/threads/new-users-cannot-access-any-smb-shares.96107/

Maybe I have the same issue?

Do newly created local (to TrueNAS) users work with SMB shares for others?