Not able to map drive to Azure File Storage share and port 445 open

Question

Has anyone outside of Msft been able to map a drive to the new preview of Azure File Storage shares without having a VPN? Our IT guy has verified that 445 is open outbound and we even contacted Comcast to verify that they are not blocking the traffic.

This is the command we are using and the error we get...

C:\Users\johndoe>net use Y: \\\\myfileshare.file.core.windows.net\\clientapps /u:myfileshare mystoragekey

System error 53 has occurred.

The network path was not found.

AzCopy works fine, but that uses https. We have tried from Windows 2012 Server and a Surface with Windows 8.1. Both support SMB3.0.

Should we be able to test telnet to myfileshare.file.core.windows.net on port 445?

Answer 1

For me it was working on Windows 8 and 10, but not Windows 8.1

I had to change the Group Policy for LAN Manager authentication level to: Send NTLMv2 responses only. I got this info from this MS answer.

https://social.technet.microsoft.com/Forums/en-US/d2ab0015-e7f7-4efb-b539-e1083d5a9d1b/azure-storage-file-service-for-onpremise-net-use-error-53?forum=windowsazuredata

I case you don't know how to open up the policy editor, see this article:

https://technet.microsoft.com/en-us/library/cc731745.aspx