locked
Storage Account - Share RRS feed

  • Question

  • Create a "storage account" and use the "share". I used the net use command to connect a Windows 10 on-premise:

    Net use t: \\ storage_name.file.core.windows.net \ sharename / u: storage_name <my_key>

    But the following error is returned:
    System error 53 has occurred. The network path was not found

    Does anyone know how to solve this?
    Friday, December 23, 2016 2:15 PM

All replies

  • Hi Davi,

    Thank you for posting here! We are happy to assist you.

    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.

    Refer here: "Error 53" or "Error 67" when you try to mount or unmount an Azure File Share
    You may also refer to Setting up a File Share for the new Azure File Service

    Regards,
    Sumanth BM
    -----------------------------------------------------------------------------------------------

    Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading the thread. And Vote as Helpful.


    Friday, December 23, 2016 7:19 PM
  • Thanks SumanthBM.

    I perform step 3 and the problem continues.
    I tested with Portqry.exe and a connection to port 445 was successful;
    My computer is Windows 10 and therefore is not enough LmCompatibilityLevel

    Do you have any other ideas?

    Regards,

    Davi

    Friday, December 23, 2016 7:54 PM
  • Hi,

    Thank you for reverting back.

    Are you referring to any documents?

    Refer here; Persisting connections to Microsoft Azure Files

    If the issue is still not rectified, for more specialized assistance on this kindly contact Azure technical support: http://azure.microsoft.com/en-us/support/options/

    Hope this helps;

    Regards,
    Sumanth BM

    Tuesday, December 27, 2016 1:05 PM
  • Sumanth BM,

    I tested it on a computer outside the domain and it worked.

    I think it's something from NTLM. The link you reported talks about NTML, but I did not find the "registry" mentioned.

    Thank you

    Tuesday, December 27, 2016 1:39 PM
  • Hi Davi,

    Thank you for reverting back!

    To clarify; Please check the region - If you have created the File share in US EAST the VM should also be in US EAST.

    1. Test the connection with the full Print Use Command in the below script:
      1. https://gallery.technet.microsoft.com/Azure-Use-Azure-File-ef3274fb
      2. Select “Print NET USE command for Windows IaaS VM.”
      3. Once the Print Use Command done try to connect again using the print use command

    2. Make sure Nslookup to the Azure File Share endpoint works:

    Example:PS C:\RD> nslookup.exe <Storage account name>.file.core.windows.net

      3.   Check if outbound TCP traffic to port  reaches Azure.

    1. Download psping ( https://technet.microsoft.com/en-us/sysinternals/jj729731.aspx )
    2. Run it as follows:>psping <name>.file.core.windows.net:***

    Azure Files only accepts NTLMv2 due to security reason, check this post for details https://technet.microsoft.com/en-us/magazine/2006.08.securitywatch.aspx

    Path: HKLM\SYSTEM\CurrentControlSet\Control\Lsa

    Change registry key LmCompatibilityLevel value back to default (3) and restart

    Note: Before making any changes to registry have a backup

    Now check the connectivity.

    Hope this helps,


    Regards,
    Sumanth BM

    Tuesday, December 27, 2016 4:28 PM
  • Sumanto BM,

    I will do the tests, however I would like to remind you that the computer that is running "netuse" is not in Azure. It's a computer on my local network.

    Regarding the "Registry" Path: HKLM \ SYSTEM \ CurrentControlSet \ Control \ Lsa: LmCompatibilityLevel key - does not exist.
    Tuesday, December 27, 2016 5:09 PM
  • Hello,

    If the issue is still not rectified, for more specialized assistance on this kindly contact Azure technical support: We would request you to create a Technical Support Ticket as our engineers would need to work with you on the issue and would require more details like on the issue. This would be beyond the purview of the Forums Support.
    https://azure.microsoft.com/en-us/support/options/

    Regards,
    Sumanth BM

    Wednesday, December 28, 2016 6:54 PM
  • Thank you!
    Thursday, December 29, 2016 1:37 PM