The Important Files (part 11): Fixing Windows 11 Samba share
All notes in this series:
- The Important Files (part 1): The goal
- The Important Files (part 2): Install FreeNAS
- The Important Files (part 3): Create a dataset and shares
- The Important Files (part 4): Setting up borg in a jail
- The Important Files (part 5): Setting up borg backup to sync.net
- The Important Files (part 6): Linux Samba share
- The Important Files (part 7): Switching to TrueNAS after 2 years powered off
- The Important Files (part 8): Setting up NAS after shipping across the Atlantic
- The Important Files (part 9): Updating rsync.net account
- The Important Files (part 10): Fixing borg backup
- The Important Files (part 11): Fixing Windows 11 Samba share
TL;DR: The Samba share permissions are determined by the TrueNAS user. By default, Windows will user the Windows user to try and authenticate, which may result in a read-only user if this does not match with the corresponding Samba user. A solution is to check “Connect using different credentials” when creating the share and use the correct user.
After upgrading from Windows 10 to Windows 11, the Samba share with my TrueNAS had become read-only. These notes document how I re-created the share to ensure it had the correct read and write permissions.
Create TrueNAS user §
In TrueNAS, go to Accounts → Users and add a user (if not already done so).
Enable Samba in TrueNas §
In TrueNAS, go to Services and ensure SMB is enabled.
Create TrueNas share §
In TrueNAS, go to Sharing → Windows Shares (SMB), and add a share.
Add Samba share in Windows §
- Open Explorer.
- Go to “This PC”.
- From the three dots menu, select “Map network drive”.
- Choose “M” for drive letter.
- Choose folder name:
\\192.168.1.10\media - Check “Connect using different credentials”. This is necessary so that you can use the user account defined on the TrueNAS, otherwise Windows will automatically default to using your Windows 11 user account.
