Hello everyone,
can anyone explain, how to configure TrueNAS SCALE in a way, that all shares will be visible?
I can access the shares directly using \\truenas\share but i want to see and “browse” all existing SMB shares by accessing \\truenas\
But i get this error in Windows:
Thanks for your help guys!
You will need to define the share mount path itself like \\TRUENAS\STUFF (or whatever you called yours).
In Windows Explorer click on ‘This PC’, then select ‘Computer’ at the top of the window, then ‘Map network drive’.
PS: Your windows user may not match the TrueNAS user from a permissions perspective.
That works, but that is not what i want.
In other environments, it’s possible to “browse” a server to see all smb shares it offers. At least in microsoft environments, that’s possible.
So i’d like to know what the difference is compared to TrueNAS, or how TrueNAS can be configured to work the same way, because: as you can see from the error, it seems to be a permission thing.
Is your Windows users username and password the same as the user on TrueNAS?
No. But that shouldn’t be an issue, because the the requirement to provide credentials does not appear before accessing a specific share.
I believe Windows might be providing your creds without you seeing and as it’s not a registered user on you NAS perhaps failing.
Could you create a user on your NAS to match your Windows client and give that a try?
We have anonymous IPC access turned off (for security reasons).
The IPC$ share is also known as a null session connection. By using this session, Windows lets anonymous users perform certain activities, such as enumerating the names of domain accounts and network shares.
That’s exactly what i want! How can i enable this in TrueNAS SCALE?
I think it’s better to create user accounts and use those.
We are using TrueNAS SCALE in a network that’s “semi-public”. It’s a hackerspace, where all people use their own devices. Everybody should be able to find and access the shares, because the data is public. Using the SMB shares anonymously is exactly what we want.
You can enable guest access to shares This downgrades the IPC security, but note that many clients will not be happy with the downgraded security 
Which means you’ll still have to deal with passwords if people are using Windows.
I already did that, but that does not solve the problem. It’s still not possible to see all existing shares (before accessing them).
yeah, i heard that Windows 10 and Windows 11 do not allow to access passwordless shares anymore. Thats why we have created 3 users with the same permissions (username=password):
“public”
“anonymous”
“guest”
That’s the most public way i can imagine.
