You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Troubleshoot issues with NFS Azure file shares.
4
4
ms.service: azure-file-storage
5
5
ms.custom: sap:Security, linux-related-content
6
-
ms.date: 01/21/2025
6
+
ms.date: 07/02/2025
7
7
ms.reviewer: kendownie
8
8
---
9
9
@@ -156,17 +156,7 @@ Unlike SMB, NFS doesn't have user-based authentication. The authentication for a
156
156
157
157
:::image type="content" source="media/files-troubleshoot-linux-nfs/connectivity-using-private-endpoints.png" alt-text="Diagram of private endpoint connectivity." lightbox="media/files-troubleshoot-linux-nfs/connectivity-using-private-endpoints.png":::
158
158
159
-
### Cause 2: Secure transfer required is enabled
160
-
161
-
NFS Azure file shares don't currently support double encryption. Azure provides a layer of encryption forall datain transit between Azure datacenters using MACSec. You can only access NFS shares from trusted virtual networks and over VPN tunnels. No extra transport layer encryption is available on NFS shares.
162
-
163
-
### Solution
164
-
165
-
Disable **Secure transfer required**in your storage account's configuration blade.
166
-
167
-
:::image type="content" source="media/files-troubleshoot-linux-nfs/disable-secure-transfer.png" alt-text="Screenshot that shows the storage account configuration blade, disabling secure transfer required." lightbox="media/files-troubleshoot-linux-nfs/disable-secure-transfer.png":::
168
-
169
-
### Cause 3: nfs-utils, nfs-client or nfs-common package isn't installed
159
+
### Cause 2: nfs-utils, nfs-client or nfs-common package isn't installed
170
160
171
161
Before running the `mount` command, install the nfs-utils, nfs-client, or nfs-common package.
172
162
@@ -233,7 +223,7 @@ sudo apt install nfs-common
233
223
234
224
---
235
225
236
-
### Cause 4: Firewall blocking port 2049
226
+
### Cause 3: Firewall blocking port 2049
237
227
238
228
The NFS protocol communicates to its server over port 2049. Make sure that this port is open to the storage account (the NFS server).
239
229
@@ -245,7 +235,7 @@ Verify that port 2049 is open on your client by running the following command. I
If you're unable to mount the file share due to **error: connection timed out**, the storage account containing the file share might be deleted accidentally.
0 commit comments