If you are trying to access the public endpoint of a storage account that has one or more private endpoints configured, you would expect to see a result that looked something like the following. For example, if you are trying to access the public endpoint of the storage account that does not have a private endpoint configured, you would see a result that looks like the following, where x.x.x.x is the IP address of the cluster. of the Azure storage platform that serves your storage account: Name : .net The output returned by Resolve-DnsName may be different depending on your environment and desired networking configuration. Resolve-DnsName -Name $hostName | Format-List # may have different suffixes than, so be sure to use the correct # Different storage accounts, especially in different Azure environments, # Replace this value with the fully qualified domain name for your storage account. # the DNS client cache to ensure you're getting the updated DNS name resolution. # If you have changed the DNS configuration in your environment, it may be helpful to clear
net) to the correct IP address for the desired network endpoint of the storage account.Įstablish a successful TCP connection to the correctly resolved IP address on the correct port for the desired protocol. To mount or access a file share successfully, your client must:īe able to resolve the fully qualified domain name of the storage account (ex. To learn more about network endpoints, see Azure Files networking considerations. The following table provides the SMB, NFS, and FileREST requirements for which of the network endpoints of a storage account they can use, and which port that endpoint can be accessed over. This can happen with any of the three file sharing protocols that Azure Files supports: SMB, NFS, and FileREST. The most common problem encountered by Azure Files customers is that mounting or accessing the Azure file share fails because of an incorrect networking configuration. Check DNS resolution and connectivity to your Azure file share You can also use the Azure file shares troubleshooter, which can help with problems connecting, mapping, and mounting Azure file shares. If you encounter problems with Azure Files, start with these steps.
Premium file shares (FileStorage), LRS/ZRS To create a new support request, sign into the Azure portal, and on the Help tab, select the Help + support button, and then select New support request. Microsoft Q&A question page for Azure Files.If you can't find an answer to your question, you can contact us through the following channels (in escalating order): It also provides possible causes and resolutions for these issues. This article lists common issues related to Azure Files.
0 kommentar(er)
