Configuring Azure VNET/VPN with FileStorage

Question

Hi,

I have an Azure VNET configured with azure file storage file shares. We have granted the fileshares access to the primary VNET and all works fine.

We now have an Azure VPN Client that is connected to the VNET - the VPN connections work fine and we can see the clients are connected to the Address Pool we have associated to it.

However, we are not able to see our Azure Fileshares when we are connected into the VPN network.

Is there an additional configuration that needs to be done?

Thank you - Greg.

Answer 1

@Greg Thomas ,

There are a few things you can check to troubleshoot this issue:

• Ensure the VPN client has the necessary permissions to access the file share. You can do this by checking the Access Control (IAM) settings for the file share in the Azure portal.
• Check the network security group (NSG) rules for the virtual network to ensure that traffic to the file share is allowed. You can do this by going to the NSG associated with the virtual network in the Azure portal and checking the inbound and outbound rules.
• Verify that the VPN client is able to reach the virtual network where the file share is located. You can do this by pinging the virtual network from the VPN client.
• Check the routing table for the virtual network to ensure that traffic to the file share is being routed correctly. You can do this by going to the virtual network in the Azure portal and checking the routes under the "Subnets" section.
• Make sure that the VPN client is using the correct DNS server. If the VPN client is using a different DNS server than the one configured for the virtual network, it may not be able to resolve the hostname of the file share.

If none of these suggestions resolve the issue, you may want to try using a network tracing tool such as Wireshark to capture traffic from the VPN client and see if you can identify any issues with the traffic.