Mount azure files

clearwatercompany 20 Reputation points
2023-03-29T13:49:54.5+00:00

Unable to Map a file share on Windows 10, When i try to map the share it gives the following error.

System error 86 has occurred.

The specified network password is not correct.

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,424 questions
{count} votes

Accepted answer
  1. Sumarigo-MSFT 47,471 Reputation points Microsoft Employee Moderator
    2023-03-29T15:19:27.7966667+00:00

    @clearwatercompany Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    Are you using Azure Storage access key or AAD for authentication?

    Based on the error message, can you please cross verify port 445 is enabled. If few Internet provider have blocked port 445, please refer to this article

    206727-image.png

    SMB has always been a network file sharing protocol. As such, SMB requires network ports on a computer or server to enable communication to other systems. SMB uses either IP Port 445 . 445 is an important port because it is used by default for all SMB communication. Windows uses it for various functions since SMB serves as the network protocol at the application level.

    I would also recommend to cross verify the prerequisites once again

    Check that you have entered the correct storage account name and file share name in the script.

    1. Check that you have entered the correct storage account key in the script.
    2. Check that the storage account key has not expired. If it has, you can regenerate the key in the Azure portal.
    3. Check that the storage account firewall is not blocking your IP address. You can add your IP address to the storage account firewall in the Azure portal.
    4. Check that your Windows machine is connected to the internet and can access the storage account.
    5. Try running the script again with the correct credentials.

    Symptoms
    You have found that the TCP port 445 is blocked.

    Customer can talk to the ISP to check if they can allow all communication to URLS ".file.core.windows.net " (Suffix used for storage accounts) and ".store.core.windows.net" (Suffix used by the storage stamp).

    Resolution:

    Solution 1 - Use Azure File Sync
    Azure File Sync can transform your on-premises Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. Azure File Sync works over port 443 and can thus be used as a workaround to access Azure Files from clients that have port 445 blocked. Learn how to setup Azure File Sync.

    Solution 2 - Use VPN
    By Setting up a VPN to your specific Storage Account, the traffic will go through a secure tunnel as opposed to over the internet. Follow the instructions to setup VPN to access Azure Files from Windows.

    Solution 3 - Unblock port 445 with help of your ISP/IT Admin
    Work with your IT department or ISP to open port 445 outbound to Azure IP ranges.

    Solution 4 - Use REST API based tools like Storage Explorer/Powershell
    Azure Files also supports REST in addition to SMB. REST access works over port 443 (standard tcp). There are various tools that are written using REST API which enable rich UI experience. Storage Explorer is one of them. Download and Install Storage Explorer and connect to your file share backed by Azure Files. You can also use PowerShell which also user REST API.

    Additional information: You can mount the file share on your local machine by using the SMB 3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage client libraries, REST APIs, PowerShell, or Azure CLI to access your files in the Azure file share.

    Azure Files only allows connections using SMB 3.0 (with encryption support) from outside the region or datacenter. SMB 3.0 protocol has introduced many security features including channel encryption which is very secure to use over internet. However its possible that port 445 has been blocked due to historical reasons of vulnerabilities found in lower SMB versions. In ideal case, the port should be blocked for only for SMB 1.0 traffic and SMB 1.0 should be turned off on all clients.

    If you still face any issue in mounting Azure file share, please let me know I would like to work closer on this issue


    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.