You can try to specify workgroup in your .smbcredentials. This should be the same as what you set under System → Services → SMB → Edit.
Also, you can try to mount this share under a windows machine.
1 Like
great suggestions! and I actually did try on windows, no access which leads me to believe i screwed something up in TrueNAS within the GUI.
can someone link me to their setup guide please? I’m looking but only found a AI chat in their Documentation Hub that is actually dumb and not giving me the info i need
Hope this helps.
That’s for dataset creation. For this test, select SMB.
When you go to change or review the dataset’s permissions, choose an “Open” ACL preset.
oh i see, so I’ll try making an ACL this time.
My current ones don’t have an ACL.
Looks like I probably changed something I wasn’t supposed to 
got this when trying to make a new data set under data/fs1 called truenasowner
[EINVAL] pool_dataset_create.share_type: Filesystem permissions on path /mnt/data/fs1 prevent access for group "builtin_users" to the path /mnt/data/fs1/truenasowner. This may be fixed by granting the aforementioned group execute permissions on the path: /mnt/data/fs1.
At minimum, every parent dataset going up to the root dataset needs “exec” permissions.
This allows users to traverse into lower directories, even if they do not have read or write permissions for the subfolders and files.
Check the permissions for the dataset data/fs1.
You can’t change the root dataset’s permissions (data), since TrueNAS restricts this in the GUI for good reason.
that makes sense, good security practice.
mind breaking this down for me lol. would that mean giving group ‘users’ exec access on FS1 then assigning the users permissions individually would work?
assuming i throw users i create into the group called ‘users’ of course. feel free to break it down to me like a 3 year old 
More than this.
From the parent dataset, with which child datasets will be assigned ownership and granted permissions, “Other” needs at minimum x permission. (Sometimes called “exec”.)
For the standard Unix permissions:
If using the ACL manager, then the particular user, group, “group@”, or “everyone@” needs to have “Traverse” permissions. (Traverse permission at minimum. Higher levels of access imply traverse permission.)
Even though the child dataset is downstream to this, the user needs to be able to trace back up the chain, up to the root dataset, with unhindered “exec” or “Traverse” permission.
Its working finally working!!! I started with what you mentioned above Winnie. it still wasn’t working but then I added the users directly ACL listing for the folder. Gave them read permissions and that did the trick.
Thanks for all the help and patience.
As the owner of TrueNAS forums I have some retrospective…
I think the UI having permission control, underneath credentials is confusing. It’s called Directories and Permissions which lead down this terrible rabbit whole and made me believe I could just add the folder permissions from there. the home directory option underneath just looked like an extra option whilst adding my permissions, the create a home directory.
That is all & signing off,
- The Owner of the TrueNAS forums -
p.s. Lars “An error occurred: Sorry, new users can only mention 2 users in a post.” i picked winnie and swc-phill, but you were great also 
2 Likes
I made this message many days ago but was blocked from posting and wanted to say thanks!
You should file a complaint to the owner of the forum.