mapping drive: System error 64 has occurred

Question

mapping drive: System error 64 has occurred

Jai Ragoo 21

Hello all, when I run the command to map my storage account on to my on-premises virtual machine I get the error:

PS C:\Windows\system32> net use j: \<STORAGE ACCT>.file.core.windows.net\share
System error 64 has occurred.
The specified network name is no longer available.

The OS is Windows 10 21H1 with SMB 3.1
The on-premises machine is joined to the on-premises AD which is sync'd with Azure AD Connect to the Azure AD.

For troubleshooting I run the following command:
Debug-AzStorageAccountAuth -StorageAccountName $StorageAccountName -ResourceGroupName $ResourceGroupName -Verbose
===> OUTPUT:
Name Result

CheckDomainJoined Passed
CheckGetKerberosTicket Passed
CheckUserRbacAssignment Passed
CheckAadUserHasSid Skipped
CheckADObjectPasswordIsCorrect Passed
CheckADObject Passed
CheckUserFileAccess Skipped
CheckPort445Connectivity Passed
CheckStorageAccountDomainJoined Passed
CheckSidHasAadUser Passed

0 comments

Answer accepted by question author

Sumarigo-MSFT 47,511 Microsoft Employee Moderator

@Jai Ragoo Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

If you have a proxy or any other kind of NAT device in his Local Network, that would be blocking the connection from On-Prem to Azure for map the Azure File Share

Add the IP Address for the Storage Account or range (x.x.x.0/24) in the proxy or NAT device.
ipconfig /flushdns & ipconfig /registerdns (Elevated cmdline)
Control Panel -> Administrative Tools -> Local Security Policy
Under Security Settings -> Local Policies -> Security Options Set "Microsoft network client: Digitally sign communications: Disable (Enabled by default)

Hope this helps
Kindly let us know if the above helps or you need further assistance on this issue.

-----------------------------------------------------------------------------------------------------------------------------------------------------

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

Jai Ragoo 21 Reputation points

2021-07-28T16:10:03.247+00:00

Thank you for the response!
I am not using a proxy.
My on-premises VM instance is behind a Cisco ASA NAT.

I am connecting across the internet, so not sure where to add that "IP Address for the Storage Account."

I disabled "Microsoft network server: Digitally sign communications (if client agrees)" and rebooted my VM but still same error.
Jai Ragoo 21 Reputation points

2021-07-28T20:22:55.453+00:00

I found that my configuration works in one of my environments and not the other. So the Azure piece is fine, the problem must then be related to the difference between the two environments. I'm marking this is resolved because the answer is related to the specific configuration of my network in which I am having trouble. Thank you!

1 additional answer

Your answer

Jai Ragoo 21 Reputation points

2021-07-28T16:10:03.247+00:00

Thank you for the response!
I am not using a proxy.
My on-premises VM instance is behind a Cisco ASA NAT.

I am connecting across the internet, so not sure where to add that "IP Address for the Storage Account."

I disabled "Microsoft network server: Digitally sign communications (if client agrees)" and rebooted my VM but still same error.
Jai Ragoo 21 Reputation points

2021-07-28T20:22:55.453+00:00

I found that my configuration works in one of my environments and not the other. So the Azure piece is fine, the problem must then be related to the difference between the two environments. I'm marking this is resolved because the answer is related to the specific configuration of my network in which I am having trouble. Thank you!

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

mapping drive: System error 64 has occurred

1 additional answer

Your answer