I have a question that isn’t directly related to TrueNAS, but it does involve it, and I’m hoping to find some knowledgeable admins here who can give me a few useful tips.
I’ve set up various NFS shares on my TrueNAS (Scale). Everything works perfectly with my Linux clients. How can I get NFS working with an old Windows 7 client? (Yes, I know Windows 7 is completely outdated! – But there’s no other option.) The Windows client only has access to TrueNAS, so no internet.
I tried installing an NFS client on Windows 7 a while back, but failed. Unfortunately, it’s been a few weeks now, so I don’t remember the details. I think it required up-to-date tools/libraries that aren’t available for Windows 7…
Sharing the DataSets in TrueNAS for both NFS and CIFS/Samba doesn’t seem to work, does it? I get issues with ACL versus Linux permissions, if I remember correctly.
I’ve now set up a VM as an NFS-to-CIFS bridge, but it’s painfully slow and impractical.
@pmh Can an SMB share and an NFS share run in parallel? That would be brilliant! I tried that at the start, but it didn’t work. I had an SMB share and then enabled the NFS share for the dataset as well. However, I couldn’t establish a connection via NFS that way. It was only when I shared the DataSet via NFS alone that I was able to connect the Linux client via NFS. SMB requires the ACL, whereas NFS requires standard Linux permissions and apparently cannot handle the ACL. My conclusion was that SMB and NFS do not work simultaneously. I don’t have much experience with NFS yet; perhaps I did something wrong?
You don’t actually need AD for this. I did this myself on Core. I used no ACLs, just regular permissions. For the SMB share, I used aux parameters to force all logged in users to a common user ID and group. Likewise for the NFS share, I mapped all logged in users to a common user and group. Then for the dataset itself, I recursively made everything owned by that common user and group.
