Skip to content

Commit 774afe9

Browse files
authored
editorial changes 2
1 parent 9f5326d commit 774afe9

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 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: 05/26/2025
7+
ms.date: 05/27/2025
88
ms.reviewer: kendownie, jarrettr, v-weizhu, v-six, hanagpal, justingross
99
---
1010
# Troubleshoot Azure Files connectivity and access issues (SMB)
@@ -145,7 +145,7 @@ 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 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 them on the Active Directory account.
148+
This issue occurs when the Active Directory computer or user account corresponding to the Azure storage account that hosts the FSLogix user profiles can't process Kerberos authentications. The underlying reasons might include incorrect modifications to the `msDS-SupportedEncryptionTypes` attribute, or the rotation of the storage account's access keys without updating the new keys on the Active Directory account.
149149

150150
#### Solution
151151

0 commit comments

Comments
 (0)