Skip to content

Commit aa90289

Browse files
authored
Update storage-troubleshoot-linux-file-connection-problems.md
Added error "No access"
1 parent 0694d6a commit aa90289

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/storage/files/storage-troubleshoot-linux-file-connection-problems.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -124,25 +124,25 @@ The encryption feature for SMB 3.0 for Linux was introduced in the 4.11 kernel.
124124

125125
If your Linux SMB client doesn't support encryption, mount Azure Files by using SMB 2.1 from an Azure Linux VM that's in the same datacenter as the file share. Verify that the [Secure transfer required]( https://docs.microsoft.com/azure/storage/common/storage-require-secure-transfer) setting is disabled on the storage account.
126126

127-
<a id="authorizationfailureportal"></a>
128-
## Error “Authorization failure” when browsing to an Azure file share in the portal
127+
<a id="noaaccessfailureportal"></a>
128+
## Error “No access” when browsing to an Azure file share in the portal
129129

130130
When you browse to an Azure file share in the portal, you may receive the following error:
131131

132-
Authorization failure
133-
You do not have access
132+
No access
133+
Error code: 403
134134

135-
### Cause 1: Your user account does not have access to the storage account
135+
### Cause 1: Virtual network or firewall rules are enabled on the storage account
136136

137137
### Solution for cause 1
138138

139-
Browse to the storage account where the Azure file share is located, click **Access control (IAM)** and verify your user account has access to the storage account. To learn more, see [How to secure your storage account with Role-Based Access Control (RBAC)](https://docs.microsoft.com/azure/storage/blobs/security-recommendations#data-protection).
139+
Verify virtual network and firewall rules are configured properly on the storage account. To test if virtual network or firewall rules is causing the issue, temporarily change the setting on the storage account to **Allow access from all networks**. To learn more, see [Configure Azure Storage firewalls and virtual networks](https://docs.microsoft.com/azure/storage/common/storage-network-security).
140140

141-
### Cause 2: Virtual network or firewall rules are enabled on the storage account
141+
### Cause 2: Your user account does not have access to the storage account
142142

143143
### Solution for cause 2
144144

145-
Verify virtual network and firewall rules are configured properly on the storage account. To test if virtual network or firewall rules is causing the issue, temporarily change the setting on the storage account to **Allow access from all networks**. To learn more, see [Configure Azure Storage firewalls and virtual networks](https://docs.microsoft.com/azure/storage/common/storage-network-security).
145+
Browse to the storage account where the Azure file share is located, click **Access control (IAM)** and verify your user account has access to the storage account. To learn more, see [How to secure your storage account with Role-Based Access Control (RBAC)](https://docs.microsoft.com/azure/storage/blobs/security-recommendations#data-protection).
146146

147147
<a id="open-handles"></a>
148148
## Unable to delete a file or directory in an Azure file share

0 commit comments

Comments
 (0)