I am unable to access a dataset on TrueNas 25.10.7 using either SMB or NFS from a win 10 machine using a drive mapping.
Error message is:
“Windows cannot access \\truenas\test_dataset\”
Dataset = test_dataset
Permissions:
owner@ - root Allow | Full Control
group@ - root Allow | Modify
Group - builtin_users Allow | Modify
Group - builtin_administrators Allow | Full Control
Group - testgroup Allow | Modify
Group = testgroup . Default configuration
User - testuser. SMB Access set. All others default.
Shares:
SMB. running.
Share ACL who*=everyone@. Full, Allowed
NFS. running
Mapall User = testuser
Mapall Group = testgroup
So, where am I screwing up?
My premise was make the dataset, make a group and give it access the the dataset. Make a user and assign them to the group.
I have deleted and then recreated the setup several times after trying every option I could think of.
one thing that bites a lot here is traverse on the parent. your share ACL can be wide open but if testuser cant traverse the pool and any parent dataset above test_dataset, windows just gives that generic cannot access error. worth double checking testuser is actually in testgroup too, then clear any old mapping for that server and map fresh using the truenas hostname plus testuser. the code under details in that windows error also helps, access denied points at permissions while a network path error points somewhere else.
I had an SMB connection issue with Windows 10 once, so I thought I’d share. I had an old Synology NAS and two Windows machines - one would work with the NAS over SMB, and the other would not. The one that would not was a newer build of Windows. Found out after quite some time that at some point, Windows deprecated SMBv1 in newer builds of Windows 10. Since my NAS and older Windows 10 machine were both set up when SMBv1 was a thing, everything was fine, but when I set up the new Windows 10 machine, it had SMBv1 disabled by default. There is a way to enable it somewhere in the OS settings, but I instead configured the NAS to serve SMBv3. If your Windows 10 machine is older, perhaps it is trying to communicate via SMBv1, but TrueNAS isn’t configured to accept that, or your TrueNAS is configured to use SMBv1, but the Windows machine is using SMBv2 or 3.
Another potential explanation would be a firewall rule blocking the traffic, which may be over port 445.
That should not be possible. We allow adjusting the minimum (for example allowing SMB1), but not adjusting the maximum (disallowing SMB3).