Notes To Self: NFS / ReadyNAS 600 / Windows 7

Microsoft's done the usual outstanding job of quality work with their NFS client.

ReadyNAS end settings:
Frontview: Share Listings->Share Name NFS

Default Access: Read-Only
Write Enabled Hosts: Self explanatory.

Root privilege-enabled hosts: Blank (unneeded)

Advanced Options: nobody/nogroup
Set ownership and permissions ... -> Apply

Squashing isn't needed on the ReadyNAS...
Via ssh to check /etc/exports:

NAS:/etc# cat exports

"/pub" *(insecure,insecure_locks,ro,async)

ReadyNAS's default nobody/nogroup = 65534.

Windows end settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousGid = FFFE
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousUID = FFFE

To check next time I screw with the Windows side: right click, properties, "NFS Attributes"-> see if setting attributes here actually work and take.

To figure out:
Network Error - 85 "The Local device name is already in use." (doesn't go away restarting NFS client (easy: nfsmgmt.msc) or workstation/server. (With mountpoints2 key removed in registry).  Where is Windows keeping the drive name until reboot, and is there a way of making it forget, so as to remount?

Further notes: Windows 7 needs -o nolock with FreeNAS, else copying gives error 0x80070021.

NFS Overview and Gotchas
Configure Windows NFS Client With Write Permissions
Steps To Disable Client For NFS Cache
Client For NFS - Configuration And Performance
Windows Mount Command syntax
NFS Share Setup For Windows 7 and Freenas

No comments: