Oracle Cloud Infrastructure Documentation

Create and Write to File System Fails using Windows NFS


To connect to file systems from Windows instances, the NFS Client must first be installed. Be sure to follow the installation procedure found in Mounting File Systems From Windows Instances before proceeding with troubleshooting.

Symptom: After installing Windows NFS client, you can successfully mount the file system from Windows, but any attempt to create or update a file in the file system fails.

Cause 1: Registry entries that map the AnonymousGid and AnonymousUid to the root user are missing or in the wrong place.

Access to NFS file systems requires UNIX-style user and group identities, which are not the same as Windows user and group identities. To enable users to access NFS shared resources, Windows client for NFS accesses file systems anonymously, using AnonymousGid and AnonymousUid. On brand new file systems, write permissions are only granted to the root user.

Solution: Verify that the correct registry entries are located in HKEY_LOCAL_MACHINE\Software\Microsoft\ClientForNFS\CurrentVersion\Default. If not, add the AnonymousGid and AnonymousUid registry entries to map them to the root user, and then remount the file system with the new user privileges.


You can verify the AnonymousGid and AnonymousUid are correctly set for a mounted file system by opening a Windows Command Line (CMD) window and typing the mount command without any arguments. A list of all mounted file systems and their properties is shown. The AnonymousGid (GID) and AnonymousUid (UID) values should appear as 0.

For example:


Local    Remote                                 Properties
X:       \\\FileSystem                  UID=0, GID=0
                                                rsize=1048576, wsize=1048576
                                                mount=soft, timeout=0.8
                                                retry=1, locking=yes
                                                fileaccess=755, lang=ANSI

If they appear as -2, they have not been correctly set. Proceed to the instructions below.

To map the AnonymousGid and AnonymousUid to the root user

Cause 2: A standard user is trying to access a file system that was mounted using the Administrator: Command Prompt (CMD). When mounting file systems, it isn't necessary to run the Command Prompt as Administrator.

Solution: Unmount the file system and then remount the file system using a standard Command Prompt. (CMD)

To remount a file system with a standard Command Prompt (CMD)