I tried tuning it but gave up and turned to NFS. But I needed to make either CIFS or NFS work in my special circumstance thanks to that old Iomega.įirst I tried CIFS since it was already configured, but it was too slow. Do not want.įrankly, SMB2 (or the newer SMB3) is the best NAS protocol for modern devices thanks to solid support from Microsoft, Apple, and Samba. AFP – Apple’s NAS protocol is rapidly falling out of favor and the open source servers are flaky to say the least.SMB2 – Apple gave up on AFP and CIFS and embraced SMB2, the way-better sequel to CIFS.NFS – The other ubiquitous protocol, NFSv3 is well-supported by most systems including the Iomega, Raspbian on the Raspberry Pi, and Mac OS X.CIFS – The Iomega runs an old version of Samba (v3.0.32 if you’re curious) that only supports CIFS, the ancient and crusty NAS protocol still sadly supported by just about everything.

There are essentially four protocols I could choose from: I also have a new Raspberry Pi 2 connected to a Drobo of its own and wanted to access its data over the network from the Mac. I have an old Iomega ix4-200d with about 2 TB of data on it and wanted to transfer that to the Drobo attached to my Mac. TL DR: NFS works (insecurely) if you use all_squash and set anonuid and anongid to match your UNIX user ID The Setup: What I Wanted to Do I had a little bit of a learning experience this week regarding NFS exports and Mac OS X that I thought would be interesting to share with my readers. It’s part “simple tip” and part “facepalm.” Read on!

Mount mac nfs share windows 10