Can't mount file share (tcp port 445)

Giulio Chessa 1 Reputation point
2022-04-30T09:35:45.527+00:00

I've tried to mount my file share

sudo mount --verbose -t cifs //logvolume.file.core.windows.net/aksshare /mnt/aksshare -o vers=3.0,credentials=/etc/smbcredentials/logvolume.cred,dir_mode=0777,file_mode=0777,serverino

but it fails with a timeout

I've opened port 443 on my linux firewall.

Please read the other details posted from this github issue of Azure Diagnostics

https://github.com/Azure-Samples/azure-files-samples/issues/102

Let me know what I have to do

Thank you

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,895 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SaiKishor-MSFT 17,221 Reputation points
    2022-05-03T19:02:52.543+00:00

    @Giulio Chessa Thank you for reaching out to Microsoft Q&A. I understand that you are having issues with mounting your file share where you get the time out error although you have opened up TCP port 445 in your firewall.

    I would suggest you go through this document regarding solving Port 445 blocked error.

    Cause 1: Port 445 is blocked
    System error 53 or system error 67 can occur if port 445 outbound communication to an Azure Files datacenter is blocked. To see the summary of ISPs that allow or disallow access from port 445, go to TechNet.

    To check if your firewall or ISP is blocking port 445, use the AzFileDiagnostics tool or Test-NetConnection cmdlet.

    The solution to this issue is also provided here in the Solution for cause 1 section. Hope this helps.

    Please let us know if you have any further questions and we will be glad to assist you further. Thank you!

    Remember:

    Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.

    Want a reminder to come back and check responses? Here is how to subscribe to a notification.

    0 comments No comments