Cannot connect to Azure File Shares from Azure VPN

ptadmin 1 Reputation point
2020-05-11T22:40:48.453+00:00

I am trying to map network drives to Azure file shares I uploaded. I can use the path provided and get the UAC prompt but, after putting in the credentials, I get a "network path not found" error. I can neither ping any of the public IPs listed for my vnet. I am connected through a Virtual Network Gateway using a P2S I created and all resources are located under the same vnet. Any advice on what is going on? Thanks.

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,897 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,280 questions
0 comments No comments
{count} votes

6 answers

Sort by: Most helpful
  1. Manu Philip 17,271 Reputation points MVP
    2020-05-12T04:47:40.747+00:00

    Hello,
    I have explained step-by-step procedure to map Azure File Share as local drive in my blog

    use-an-azure-file-share-with-windows

    Please check, if you are following the same strategy for mapping the drive

    Thanks,
    Manu

    0 comments No comments

  2. ptadmin 1 Reputation point
    2020-05-12T15:24:20.613+00:00

    It did not work. The command you provided failed to run due to positional parameters that cannot be found.

    0 comments No comments

  3. Manu Philip 17,271 Reputation points MVP
    2020-05-13T05:07:33.247+00:00

    Hello,
    Sorry to see that you are still experiencing some issues. I am putting all the steps together as below. The steps will work as I tested now.

    1. Create a azure resource group. Change name and location as preferred New-AzResourceGroup -Name manazrg -Location southindia
    2. Create the new storage account. Change the resource group name, use your preferred storage group name, location. I have selected the SKU - Standard_LRS New-AzStorageAccount -ResourceGroupName manazrg -Name manuazsg -Location southindia -SkuName Standard_LRS
    3. Find the secret key. Change the resource group name, storage group name. Copy any one of the key Get-AzStorageAccountKey -ResourceGroupName “manazrg” -AccountName manuazsg
    4. Substitute the key in the following cmdlet to create the required share. Change resource group name, any one of the key key $azShare = New-AzStorageContext “manazsg” “your key here”
    5. Create share. Use your preferred share name New-AzStorageShare manaznetshare -Context $azShare
    6. From windows explorer, click ‘Map Network Drive’. Substitute, your storage groupname, share name below:

    Share name: \manazsg.file.core.windows.net\manaznetshare

    Username, Password:
    AZURE\<storage account name> and Password is your key copied in step 3

    1. This will bring up the share in your windows explorer :)

    Regards,
    Manu

    0 comments No comments

  4. Stephane Budo 426 Reputation points
    2020-05-19T03:27:40.423+00:00

    Hi,

    I'm a little confused on the architecture of the solution:
    You mentioned you are connecting to a VNet in Azure with a P2S connection. Is this to connect to existing virtual machines?
    The Azure File Share is part of the storage offering which is a public service. This mean that the access will be done through a public IP, so there is no need for VPN.
    Or did you create an endpoint within the VNet for the storage account and are trying to map the drives from your VMs located on your VNet?
    For troubleshooting purposes, have you tried to connect directly to the file share from your local computer (outside of Azure) through a simple internet connection?

    Thank you,
    Stephane

    0 comments No comments

  5. ptadmin 1 Reputation point
    2020-05-19T04:04:19.743+00:00

    Hello,

    I found a YouTube video which explained why I could not connect. There were some ways I needed to adjust the VPN on the client so it could communicate with the VPN and private endpoint I created. Thanks anyway.