Hi, Is this expected behavior? I’ve been playing around with SMB permissions and noticed Windows 11 not recognizing dataset permission changes right away. One time I was able to correct the situation by rebooting FreeNAS. I didn’t try rebooting Windows. Other times they just took effect seemingly at random at a later time.
Welcome to Windows and SMB. This happened to me all the time when I was a heavy SMB user, generally reconnecting the Windoze device to the SMB share will solve this.
Are you talking about viewing permissions through file explorer, effective permissions for an established SMB session, or something else?
Through file explorer. Also having an effective SMB session. I was having issues where i was able to modify when i shouldn’t or not view when i should , etc.
To clarify, you’re talking about viewing through the security tab in File Explorer?
No, just issues accessing or not accessing the files not according to the permissions o had set up in TrueNAS.
I have another question maybe related. So the question is, what’s going wrong with this? When I make a dataset read only, I can rename any of the files and folders beneath the top level folders, unless i apply permissions recursively. But SMB means the child folders inherit the parent folder permissions, isn’t it?
The way i make it read only is first strip the ACLs, then apply NF4_OPEN preset, then change the owner@, group@, and everybody@ permission to read.
Sorry i just realized maybe i should ask why you no longer use SMB. Should i be looking to switch to Unix share?