Applicable Products
- All QNAP NAS series
- Windows Server (any supported version)
Scenario
A user accesses a QNAP NAS shared folder via Network File Services (NFS) from a Windows Server running a supported version. When copying a file with the same name, Windows displays the Replace or Skip Files prompt, indicating that an existing file is present on the NAS.
However, after selecting Replace the file in the destination, the operation fails with an access denied or permission error, preventing the file from being overwritten or updated.
Root Cause
This behavior is a known limitation of the Client for NFS feature in Windows Server and is independent of the NAS configuration. The same behavior is observed across all supported Windows Server versions that include Client for NFS.
- Client for NFS supports only NFSv2 and NFSv3 and does not support NFSv4 ACLs. As a result, it cannot negotiate or modify POSIX ACLs over NFS.
- By default, Client for NFS accesses NFS shares using an anonymous UID and GID. If the NAS does not grant write permissions to this anonymous identity, write operations fail.
- Access is denied unless the anonymous UID and GID are explicitly mapped to a UID and GID that the NAS recognizes and allows to write to the shared folder, regardless of the shared folder’s configured write permissions.
Note
These settings must be configured on the Windows Server.
Solution
To resolve this issue, map the anonymous NFS user on the Windows Server to a UID and GID that the NAS allows to write to the shared folder.
You can apply the configuration using one of the following methods.
Method 1: Configure Using PowerShell (Recommended)
- Open PowerShell as an Administrator.
- Launch PowerShell with administrative privileges.
- Run the following commands to map the anonymous UID and GID to
0, which corresponds to the QNAP root user.Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default" -Name AnonymousUid -Value 0 -PropertyType DWord
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default" -Name AnonymousGid -Value 0 -PropertyType DWord
- Run the following command to restart Client for NFS or reboot the system to apply the changes:
nfsadmin client restart
Tip
Alternatively, you can restart the Windows Server.
Method 2: Configure Using the Windows Registry
- Press Win + R.
- Type
regedit. - Press Enter.
- Navigate to the following registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default
- Go to Edit > New, and then click DWORD (32-bit) Value.
- Create the following two DWORD (32-bit) values inside the default folder:
- AnonymousUid = 0
- AnonymousGid = 0
- Apply the changes by restarting the NFS client:
nfsadmin client restart
Tip
Alternatively, you can restart the Windows Server.
Important
- Mapping the UID and GID to
0 allows Client for NFS to access the NAS as the root user. Ensure that the NAS shared folder grants write permissions to this identity. - Apply these settings on each Windows Server that accesses the NFS share.
- This applies to all Windows versions that support the Client for NFS feature.
- For environments that require fine-grained permission control or NFSv4 ACL support, Windows Server acting as an NFS client is not supported.
Further Reading
適用產品
- All QNAP NAS series
- Windows Server (any supported version)
情境
使用者透過網路檔案服務 (NFS) 從執行支援版本的 Windows Server 存取 QNAP NAS 共享資料夾。當複製同名檔案時，Windows 顯示 取代或跳過檔案 提示，表示 NAS 上已存在檔案。
然而，選擇 取代目的地的檔案後，操作因存取被拒或許可權錯誤而失敗，無法覆寫或更新檔案。
根本原因
此行為是 Windows Server 中 NFS 使用者端功能的已知限制，與 NAS 設定無關。在所有包含 NFS 使用者端的支援 Windows Server 版本中均可觀察到相同行為。
- NFS 使用者端僅支援 NFSv2 和 NFSv3，不支援 NFSv4 ACL。因此，無法透過 NFS 協商或修改 POSIX ACL。
- 預設情況下，NFS 使用者端使用匿名 UID 和 GID 訪問 NFS 共享。如果 NAS 未授予此匿名身份寫入許可權，則寫入操作失敗。
- 除非匿名 UID 和 GID 明確對映到 NAS 認可並允許寫入共享資料夾的 UID 和 GID，否則存取被拒，無論共享資料夾的寫入許可權如何配置。
註
這些設定必須在 Windows Server 上配置。
解決方案
要解決此問題，請將 Windows Server 上的匿名 NFS 使用者對映到 NAS 允許寫入共享資料夾的 UID 和 GID。
您可以使用以下方法之一應用配置。
方法 1：使用 PowerShell 配置 (推薦)
- 以系統管理員身份開啟 PowerShell。
- 啟動 PowerShell，並具有管理許可權。
- 執行以下命令以將匿名 UID 和 GID 對映到
0，對應於 QNAP root 使用者。Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default" -Name AnonymousUid -Value 0 -PropertyType DWord
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default" -Name AnonymousGid -Value 0 -PropertyType DWord
- 執行以下命令以重新啟動 NFS 使用者端或重啟系統以應用更改：
nfsadmin client restart
提示
或者，您可以重新啟動 Windows Server。
方法 2：使用 Windows Registry 配置
- 按下 Win + R。
- 輸入
regedit。 - 按下 Enter。
- 導航至以下登入路徑：
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default
- 前往 編輯 > 新增，然後按一下 DWORD (32 位元) 值。
- 在預設資料夾中建立以下兩個 DWORD (32 位元) 值：
- AnonymousUid = 0
- AnonymousGid = 0
- 重新啟動 NFS 客戶端以套用變更：
nfsadmin client restart
提示
或者，您可以重新啟動 Windows Server。
重要
- 將 UID 和 GID 對映至
0允許 NFS 客戶端以 root 使用者身份存取 NAS。確保 NAS 共享資料夾授予此身份寫入許可權。 - 將這些設定應用於每個存取 NFS 共享的 Windows Server。
- 這適用於所有支援 NFS 客戶端功能的 Windows 版本。
- 對於需要細緻許可權控制或 NFSv4 ACL 支援的環境，Windows Server 作為 NFS 客戶端是不支援的。
進一步閱讀
