Failed to map drive to Azure storage port and open port 445

Question

Has anyone besides Msft been able to map the drive to a new preview of Azure File Storage shares without a VPN? Our IT professional confirmed that 445 is open outgoing, and we even contacted Comcast to make sure that they are not blocking traffic.

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

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 uses https . We tried with Windows 2012 Server and with a surface with Windows 8.1. Both support SMB3.0.

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

Answer 1

For me, this worked on Windows 8 and 10, but not on Windows 8.1

I had to change the group policy for the LAN Manager authentication level to: Send only NTLMv2 responses. I got this information from 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

In case you do not know how to open the policy editor, see this article:

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

Answer 2

I have the same problem. It happens that I can use the NET USE command in some hosts, while in others it gives me an error 53. On another host, I really get an access error that was denied.

It works fine in one Windows 10. On the other 3 I tried, it does not work fine. It also works fine on Windows 2008 R2, which is used as the dev environment, but it does not work on others.

I have no problem using Azure Powershell CMDlets.

Answer 3

When I called Comcast, they told me that 445 was blocked. I created azure vm and confirmed that the command is correct. Was able to display my drive within Azure. took the same team in place and continued to get the same error you were talking about. I would double check that comcast really has open ones.