Skip to content

Commit 5772996

Browse files
authored
editorial changes
1 parent b967795 commit 5772996

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Troubleshoot problems connecting to and accessing SMB Azure file sh
44
services: storage
55
ms.service: azure-file-storage
66
ms.custom: sap:Connectivity, devx-track-azurepowershell, linux-related-content
7-
ms.date: 04/24/2025
7+
ms.date: 05/26/2025
88
ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal, justingross
99
---
1010
# Troubleshoot Azure Files connectivity and access issues (SMB)
@@ -145,13 +145,13 @@ When mounting a file share from on-premises or another datacenter, you might see
145145

146146
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.
147147

148-
This issue definitively occurs when the Active Directory Computer or User account corresponding to the Azure Storage Account hosting the FSLogix user profiles is unable to process Kerberos authentications. The underlying reasons could be incorrect changes to the msDS-SupportedEncryptionTypes attribute or rotation of Azure Storage Account's Access Keys without updating it on the Active Directory account.
148+
This issue occurs when the Active Directory computer or user account corresponding to the Azure storage account hosting the FSLogix user profiles can't process Kerberos authentications. The underlying reasons could be incorrect changes to the `msDS-SupportedEncryptionTypes` attribute or the rotation of the storage account's access keys without updating it on the Active Directory account.
149149

150150
#### Solution
151151

152152
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.
153153

154-
Kerberos errors will be visible in a network trace (e.g. flows tagged as KRB Error in case of a netsh trace). To resolve, follow the steps to enable Active Directory Domain Services authentication for Azure file shares (https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-enable) to set up the authentication parameters properly.
154+
Kerberos errors can be seen in a network trace, such as flows labeled as KRB Error in a netsh trace. To resolve them, [enable Active Directory Domain Services authentication for Azure file shares](/azure/storage/files/storage-files-identity-ad-ds-enable) to set up the authentication parameters properly.
155155

156156
### <a id="error-0x800704b3"></a> Failed with error code 0x800704b3
157157

0 commit comments

Comments
 (0)