Merge pull request #8787 from MicrosoftDocs/main

Auto push to live 2025-04-24 02:31:10

Author: Deland-Han

support/azure/azure-storage/files/connectivity/files-troubleshoot-smb-connectivity.md

@@ -4,8 +4,8 @@ description: Troubleshoot problems connecting to and accessing SMB Azure file sh
 services: storage
 ms.service: azure-file-storage
 ms.custom: sap:Connectivity, devx-track-azurepowershell, linux-related-content
-ms.date: 02/04/2025
-ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal
+ms.date: 04/24/2025
+ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal, justingross
 ---
 # Troubleshoot Azure Files connectivity and access issues (SMB)
 
@@ -135,6 +135,20 @@ Revert the `LmCompatibilityLevel` value to the default value of 3 in the followi
 
 `HKLM\SYSTEM\CurrentControlSet\Control\Lsa`  
 
+### <a id="error-64"></a> Error 64 when you mount an Azure file share
+
+When mounting a file share from on-premises or another datacenter, you might see the following error:
+
+> System error 64 has occurred. The specified network name is no longer available.
+
+#### Cause
+
+This issue is likely caused by a proxy server or another type of Network Address Translation (NAT) device in the datapath that blocks the connection to map the Azure file share. In this case, the PowerShell cmdlet `Test-NetConnection` still might test connectivity on port 445 successfully.
+
+#### Solution
+
+To resolve this issue, reproduce it and collect a network trace to get more information about the error's origin. In most cases, you must work with your network/firewall administrator to allow the content to pass through the network device.
+
 ### <a id="error-0x800704b3"></a> Failed with error code 0x800704b3
 
 When you try to mount an Azure file share, you receive the following error:

support/azure/azure-storage/files/security/files-troubleshoot-smb-authentication.md

@@ -75,7 +75,7 @@ First, make sure that you've followed the steps to [enable Azure Files AD DS Aut
 
 Second, try [mounting Azure file share with storage account key](/azure/storage/files/storage-how-to-use-files-windows). If the share fails to mount, download [AzFileDiagnostics](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Windows) to help you validate the client running environment. AzFileDiagnostics can detect incompatible client configurations that might cause access failure for Azure Files, give prescriptive guidance on self-fix, and collect the diagnostics traces.
 
-Third, you can run the `Debug-AzStorageAccountAuth` cmdlet to conduct a set of basic checks on your AD configuration with the logged-on AD user. This cmdlet is supported on [AzFilesHybrid v0.1.2+ version](https://github.com/Azure-Samples/azure-files-samples/releases). 
+Third, you can run the `Debug-AzStorageAccountAuth` cmdlet to conduct a set of basic checks on your AD configuration with the logged-on AD user. This cmdlet is supported on [AzFilesHybrid v0.1.2+](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFilesHybrid).
 
 1. Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account:
 
@@ -147,7 +147,7 @@ Debug-AzStorageAccountAuth `
 
 First, make sure that you've followed the steps to [enable Microsoft Entra Kerberos authentication](/azure/storage/files/storage-files-identity-auth-hybrid-identities-enable).
 
-Second, you can run the `Debug-AzStorageAccountAuth` cmdlet to perform a set of basic checks. This cmdlet is supported for storage accounts configured for Microsoft Entra Kerberos authentication, on [AzFilesHybrid v0.3.0+ version](https://github.com/Azure-Samples/azure-files-samples/releases).
+Second, you can run the `Debug-AzStorageAccountAuth` cmdlet to perform a set of basic checks. This cmdlet is supported for storage accounts configured for Microsoft Entra Kerberos authentication, on [AzFilesHybrid v0.3.0+](https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFilesHybrid).
 
 1. Sign in to Azure PowerShell interactively as an AD user that has owner permission on the target storage account: