John M. Długosz
Contributor
- Joined
- Sep 22, 2013
- Messages
- 160
The FreeNAS docs explain that NFS can have better performance than CIFS, and gives directions for installing 3rd party NFS solutions on versions of Windows that don't support it directly. I want to take advantage of that, so I enabled NFS (supported by "Ultimate") and indeed connected to the FreeNAS box.
But, although I can browse the directories and see the file names, all files give errors that they are locked by some other process, and can't be read.
I tried turning off the Samba service completely in case there were some residual effects. It did not make a difference.
Now this shouldn't be any harder than serving NFS on one end and using NFS on the other, and the docs don't mention any other funny business. The permissions are OK since it worked on CIFS for the same directory, and the error doesn't indicate that it's a permissions problem. But I wonder if it still might be, and Windows doesn't interpret the error correctly? Do NFS shares have some access rules supplied directly onto the share, or interpret things differently than Samba might, or anything?
—John
But, although I can browse the directories and see the file names, all files give errors that they are locked by some other process, and can't be read.
I tried turning off the Samba service completely in case there were some residual effects. It did not make a difference.
Now this shouldn't be any harder than serving NFS on one end and using NFS on the other, and the docs don't mention any other funny business. The permissions are OK since it worked on CIFS for the same directory, and the error doesn't indicate that it's a permissions problem. But I wonder if it still might be, and Windows doesn't interpret the error correctly? Do NFS shares have some access rules supplied directly onto the share, or interpret things differently than Samba might, or anything?
—John