Problems mapping Azure file shares on-premises

Occasional Visitor

Hi. I'm new to Azure. I'm an MSP and a Microsoft Partner. I just created my Storage Account and first file share. I'm trying to map the file share from an on-premises Windows 10 workstation and Windows Server 2012. Neither work. I keep getting the error "network path not found"...error code 0x80070035. I tried to map the drive using PowerShell and Windows map drive from the GUI using the instructions for the Azure Portal (connect). I have verified that port 445 is open. Is this supported from on-premises locations?

6 Replies

I too have ran into this. Would love to know what the solution is.


I found this PS script which is pretty great:

But it still returns this error=

[ERROR]: Map drive failed and Net use returns the error: System error 1311 has occurred.  We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

No, the problem isn’t with creating the File Share. It’s with mounting it in Windows 10 Pro - mapping it.

This link is more relevant but I have yet to find a solution to the System Error I’m experiencing.

Did you test all tests in I have the same problems and did find out that 445 is closed.

As embarrassing as this is, my issue was resolved by completely uninstalling Bitdefender. Even though I had manually entered rules / exceptions - it was apparently still blocking the connection for some unknown reason. Completely uninstalling Bitdefender allowed me to map the drives without issue.
Hi, you better do the test as an Admin, sign in azure in the same PC/Server. check your privacy and permission.
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.
To learn about ways to work around a blocked 445 port, see the Cause 1: Port 445 is blocked section of our Windows troubleshooting guide.