Azure map drive system error 53 has occurred

Question

I am trying to map a storage account to a Virtual machine in Azure.

I am following a simple tutorial which details how to access your Azure Files from inside a VM.

You simply create a new storage account so that it has the new Azure Files access, then map a drive to the VM using net use:

net use z: \\tempstorage.file.core.windows.net\upload /u:tempstorage mykey

I am getting:

System error 53 has occurred.
The network path was not found.

I have made the container public and can access files located inside via the url:

https://tempstorage.blob.core.windows.net/upload/example.jpg

Any ideas why I am getting System error 53?

Please note: the above urls are an examples and don't link to a read locations.

Deliquescence

I think you're getting confused between blob storage and file service. It seems you created a blob container in your"tempstorage" account but trying to mount as file service. What you would need to do is create a file service share called "upload" in file service and then mount that. – Augustin

No, I am using the new Files Preview which allows you to access blob storage via a file share – Deliquescence

No, I think that's where you're incorrect. Files Service and Blob Storage are two different services offered by Azure. You can't share blob containers via File Service. As I mentioned in my comment above, you would need to create a "Share" in your file service (which is like blob container) and then mount that in your VM. But you can't mount a blob container. – Augustin

I see, they are completely different services. – Deliquescence

Possible a duplicate of this question. – Haematosis

Answer 1

You need to make sure that you have first enabled that folder as a Share. See step 3 on this blog:

http://blogs.msdn.com/b/windowsazurestorage/archive/2014/05/12/introducing-microsoft-azure-file-service.aspx

If you don't do this then you won't be able to map it to a virtual machine using the 'net use' command.

Misspend

This seems like a possible answer, but the blog entry doesn't make it clear what step enables the folder as a share. I'm using the Portal web page, and have created the file share. I then clicked on the "Connect" button for the file share, which simply displays a message giving the net use command to use. Issuing that command (with my storage key and drive letter) still gives the System error 53 has occurred message. – Recruit

Answer 2

Change this registry key to a value of 3

HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LmCompatibilityLevel

For more information, see the LmCompatibilityLevel topic on TechNet.

Got this solution from this MS docs

Hammered

Note that MS says this requires a reboot to take effect but in my testing it worked straight away. – Acquah