question

HenryPhan-7182 avatar image
0 Votes"
HenryPhan-7182 asked deherman-MSFT answered

Azure File Point-To-Site

Followed every step in this:

https://github.com/Azure-Samples/azure-files-samples/tree/master/point-to-site-vpn-azure-files#step-3---deploy-arm-template-to-create-vnet-and-p2s-vpn-gateway

And I was able to get the Azure VPN to work with the certificates. However when on

Step 6 - Persist and mount Azure File Share

I get this error: New-PSDrive: The network resource type is not correct.

Also I did run nslookup { }.file.core.windows.net
And got the an answer back


Anybody got any ideas?





azure-files
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AlanKinane avatar image
0 Votes"
AlanKinane answered
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

deherman-MSFT avatar image
0 Votes"
deherman-MSFT answered

@HenryPhan-7182

Double check the Prerequisites article again and cross verify that you have completed the all the prerequisites requirements. If the requirements have been completed, refer to the below mentioned article.

Use AzFileDiagnostics script to ensure that the Windows client environment has correct prerequisites. AzFileDiagnostics automates detection of most of the symptoms mentioned in this article and helps set up your environment to get optimal performance. You can also find this information in the Azure Files shares Troubleshooter that provides steps to assist you with problems connecting/mapping/mounting Azure Files shares.

If the issue still persist, kindly share the below mentioned details:
1. What all OS version has been deployed in the other(client) computer( Also refer here for OS version supported in Azure File share)?
2. Ensure all 445 port is enabled in all computers?
3. Location where File Share is being mounted
4. To determine whether this is the cause of the error, verify that the following registry subkey is set to a value of 3:HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LmCompatibilityLevel. For more information, see the LmCompatibilityLevel topic on TechNet.
5. The name of your file share must be all lowercase. For complete details about naming file shares and files, see Naming and referencing shares, directories, files, and metadata. Please check if NTLMv1 communication is enabled on the client. Azure Files supports only NTLMv2 authentication. Having NTLMv1 enabled creates a less-secure client. Therefore, communication is blocked for Azure Files.
6. If the issue still persist, please share the screen shot of the error message.

Hope this helps. Let me know if you are still facing issues and we can work with you directly to resolve the issue.



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


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.