Cannot map Azure File Share

Question

I am trying to access a file share on an Azure storage account from an Azure VM in the same virtual network / subnet.

When I perform an nslookup on my storage account i get the following

nslookup (name of storage account).file.core.windows.net

Non-authoritative answer:
Name: file.phx10prdstr02a.store.core.windows.net
Address: 20.60.14.200
Aliases: (name of storage account).file.core.windows.net

(name of storage account).privatelink.file.core.windows.net

The nslookup responds with the alias of 'privatelink' which I believe means the private endpoint is set up correctly.
This Private endpoint has an IP address assigned of 10.0.0.10.

Instead of using DNS I am trying to map the share via IP address. (I know DNS is preferred but not ready for that yet)

Next I try to map the drive from the Azure VM

======
net use z: \ 10.0.0.10(name of file share)
System error 53 has occurred.

The network path was not found.

What am I doing wrong?

Answer 1

For anybody else having this problem, here was how I resolved my issue.
I downloaded AzDiagnostics.ps1 from git hub and ran it against my storage account/fileshare on my Azure VM
Instructions here on how to download:
https://github.com/Azure-Samples/azure-files-samples/tree/master/AzFileDiagnostics/Windows

Download the zip and look for the AzFileDiagnostics.ps1 file located in "azure-files-samples-master\azure-files-samples-master\AzFileDiagnostics\Windows"

I then ran:
.\AzFileDiagnostics.ps1 -UNCPath \storageaccountname.file.core.windows.net\sharename

The output showed me my LmCompatibility Level in "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa" was set to 1. It stated it needed to be 3 or mounting shares would fail.

I changed to 3 and reran the map drive power shell script. Boom! All good now.

Also found the below on MS docs. Great info
https://learn.microsoft.com/en-us/answers/questions/727502/azure-file-share-mount-issue.html

Answer 2

@Joshua Thompson Welcome to Microsoft Q&A Forum, Thanks for posting your query here!

Based on the error message, Issue may be occurred due port 445 is been blocked. Ensure port 445 is open: The SMB protocol requires TCP port 445 to be open; connections will fail if port 445 is blocked. You can check if your firewall is blocking port 445 with the Test-NetConnection cmdlet.

Note: Some of the ISP provide has blocked port 445 for azure files, please check here

Error : System error 53 has occurred. The network path was not found. , Please refer to the troubleshooting steps mentioned in this article.

This thread provides detailed steps " How to Map the Azure file share to a Windows drive(Azure VM)"

Please let us know if you have any further queries. I’m happy to assist you further.

----------

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