Hi – I have had FreeNAS/TrueNas Core running well on an old Dell R710 for a few years. I have the latest update to Core installed.
Recently I have not been able to access my Windows Share dataset from either my desktop PC (Windows 11) or my Apple silicon MacBook Pro.
Both machines appear to “see” the server (“FREENASSERVER” – so creative!), as FREENASSERVER shows up under their respective file manager Network listings.
However, whenever I try to access my Windows share dataset, both return “can’t find it” errors. I have tried editing ACL permissions to let anyone in, adding ACL users for each of the PC and the Mac, adding a new user, turning SMB service off/on after each change, restarting the server, etc. I also returned to the TrueNAS tutorial for pools/datasets/users to see whether I had forgotten the basics.
I have no doubt that the problem is something simple and obvious – likely a setting I no doubt screwed up as I’ve been mucking about (for which I will kick myself once discovered).
Since you’re a new user, please browse a few other forum thread and, if you haven’t already, take the tutorial. We need to get your forum trust level up so you have more posting rights.
TrueNAS-Bot
Type this in a new reply and send to bring up the tutorial, if you haven’t done it already.
@TrueNAS-Bot start tutorial
Nice first post as it contains a lot of info on what you have attempted. Did the problems start after a TrueNAS update or it just seemed to happen, no possible cause?
Examples from my Core machine on how I have it set up
Shay is my base pool. BU2 is the child dataset created for SMB sharing
Thank you so much for responding. Unfortunately, I cannot tell whether it is the update or my actions which have caused the access issues (more likely the latter, though). When I opened the TrueNas console I saw the available update and installed it before doing anything else, but then immediately started to try to figure out why my MacBook Pro could not access the dataset that I had set up for TimeMachine. Obviously, in hindsight I should have checked that all else was well before mucking about.
After you get your trust level up, post the screens I had as examples so we can see how you have it set up. I usually use the snipping tool for the screen shots and trimming in Windows.
What version of Core are you on. You can copy and paste from the GUI Dashboard. Usually on the first page.
Your setup is different from my simple setup. I am not sure what is conflicting. You don’t have the share owner as root, that’s good as root can’t share SMB. Check your users pages for your two users and make sure they have the SMB or SAMBA box checked to allow sharing.
Did you need access right away or can this wait to see if someone replies over the weekend.? I am not sure if you need certain settings for the OS-X. I only share to a windows machine. The WHEEL group on my machine doesn’t allow SAMBA Auth. Check yours, you may have to unhide the built in users to see it. Root and Wheel don’t have SAMBA Auth any more by default. my ACL Mode is set to Passthrough and you have Restricted.
If you don’t want to wait for others to comment, you can try changing the settings to match mine.
