Hi @Jorge Ramirez ,
There are a number of connection issues and Azure file configuration issues that can trigger the hardcoded error.
Can you verify that you used the full net use command from the Azure AD DS page?
$connectTestResult = Test-NetConnection -ComputerName <storage-account-name>.file.core.windows.net -Port 445 if ($connectTestResult.TcpTestSucceeded) { net use <desired-drive letter>: \\<storage-account-name>.file.core.windows.net\<fileshare-name> } else { Write-Error -Message "Unable to reach the Azure storage account via port 445. Check to make sure your organization or ISP is not blocking port 445, or use Azure P2S VPN, Azure S2S VPN, or Express Route to tunnel SMB traffic over a different port." }
When you run the Test-NetConnection you should get the PingSucceeded as True if 445 is not blocked.
Note that your client OS should support SMB 3.0 and you need to make sure this SMB Direct option is enabled in your windows system. (See related Stack Overflow post.)
Also, have you tried mounting it using File Explorer to see if there is a difference?
If you haven't already, I would recommend using the AzFileDiagnostics script to verify if Port 445 is being blocked by your ISP (even if it isn't being blocked in Azure).
If the ISP is blocking port 445 you do need to use a VPN to connect to the file share to avoid this issue. You can use P2S or S2S and/or Express Route, or you can contact the ISP to ask if opening port 445 is an option.
I have also seen this issue before when there were manual domain objects preventing AD Auth, in which case a support case may be required to resolve this.
I've reached out to my contacts on the Storage team to look into your case as they will have additional troubleshooting steps to recommend.
-
If the information helped you, please Accept the answer. This will help us and other community members as well.