User Tools

Site Tools


microsoft_windows:nfs_client

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
microsoft_windows:nfs_client [2025/03/27 00:19] rodolicomicrosoft_windows:nfs_client [2025/03/27 00:45] (current) rodolico
Line 3: Line 3:
 Microsoft Windows can attach to NFS Shares with no problem, though you must use the command line to do it. You also need to install the NFS Client Role (Server) or package (Workstation) as it is not normally turned on. Microsoft Windows can attach to NFS Shares with no problem, though you must use the command line to do it. You also need to install the NFS Client Role (Server) or package (Workstation) as it is not normally turned on.
 **Note**: everything other than the basic read-only mount requires rebooting the server. This **must** be done for it to work (because it is Microsoft, and . . . ) **Note**: everything other than the basic read-only mount requires rebooting the server. This **must** be done for it to work (because it is Microsoft, and . . . )
 +
  
 ===== Read-only access ===== ===== Read-only access =====
Line 10: Line 11:
 </code> </code>
  
-===== Read/Write Access as anon =====+===== Read/Write Access as anon (anonymous user) =====
 To get read/write access, you will need to go a step further. If you do not care about mapping Windows users to users on your NFS server, you can just go in as the anonymous user (anon). Note that this will kill all restrictions. Anyone who can connect can read/write/delete any file in the target. To get read/write access, you will need to go a step further. If you do not care about mapping Windows users to users on your NFS server, you can just go in as the anonymous user (anon). Note that this will kill all restrictions. Anyone who can connect can read/write/delete any file in the target.
  
Line 80: Line 81:
 </code> </code>
  
 +===== General Notes =====
 +
 +I do not go over them below, but everything is mounted with file access of 755 (read/write owner, read only for everyone else) and case insensitive (standard Windows). The mount is not persistent and will not survive a logout/login. Also, the mount is for the current user only. 
 +
 +The default behavior can be modified with some additional flags to the mount command
 +  * -o fileaccess=777 # gives full read/write to anyone who can get to this
 +  * -o fileaccess=700 # owner can do everything, everyone else can not even read it
 +  * -o casesensitive=yes # makes file access case sensitive, standard Unix
 +
 +You can also create a startup script to auto-mount the volume when you log in. See the article [[microsoft_windows:autostart|]] for some hints on that.
 +
 +To make the mapping persistent, there are hints at https://marcoschiavon.net/mount-a-share-for-all-users-on-a-windows-server/ which I have not tried.
 +
 +Finally, the mount command is your friend. **mount** just by itself will show all mounts with all parameters 
  
 ===== Thank you ===== ===== Thank you =====
microsoft_windows/nfs_client.1743052761.txt.gz · Last modified: 2025/03/27 00:19 by rodolico