"Port 445 is not reachable from this client" depsite vn-p2s-vpn connection

Cataster 641 Reputation points
2021-09-02T06:10:16.83+00:00

I am trying to connect my azure storage file share and mount as a network/shared drive, but its failing. 

PS C:\Users\> $connectTestResult = Test-NetConnection -ComputerName analyticsdev.file.core.windows.net -Port 445                                                                WARNING: TCP connect to (52.XXX.XXX.XX : 445) failed                                                                                                                                         WARNING: Ping to 52.XXX.XXX.XX failed with status: TimedOut

I ran the script in regular (non-elevated) powershell mode, as well as enabled Azure P2S VPN per the suggestion:

128581-image.png

128438-image.png

128425-image.png

This is a follow-up form this question here, where I tried Luis's method to map a Azure Blob storage but it didnt work. Apparently, only file shares can be mapped, not blob containers?

Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,171 questions
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,728 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,455 questions
Windows Server PowerShell
Windows Server PowerShell
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.PowerShell: A family of Microsoft task automation and configuration management frameworks consisting of a command-line shell and associated scripting language.
5,390 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,406 Reputation points
    2021-09-02T11:29:43.407+00:00

    Hello Cataster,

    Thank you for coming back to the forum!

    Unfortunately there is no way to map blob containers. Not long ago there was the same discussion in another thread, you can see the community options and options here:

    https://social.msdn.microsoft.com/Forums/en-US/e5d79b0b-5a2b-4dcc-8571-6ff9b973efb9/map-a-blob-storage-as-network-drive?forum=windowsazuredata

    Best regards!

  2. Limitless Technology 39,406 Reputation points
    2021-09-02T17:56:01.45+00:00

    Hello again @Cataster

    Error clearly says that you should run powershell as normal (Not as Admin) also try to check if TCP port 445 is blocked in Azure as well as in your computer (Check ICMP is allowed or not in Firewall ).

    If port 445 is blocked by your organization's policy or by your ISP, you can use Azure File Sync to access your Azure file share.

    Azure File Sync - https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal

    Also, there has already been some feedback around this topic and I’d encourage you to upvote it by visiting the link:

    https://learn.microsoft.com/en-us/answers/questions/112921/unable-to-connect-to-my-azure-file-share-from-both.html

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    Thanks,

  3. Sumarigo-MSFT 43,816 Reputation points Microsoft Employee
    2021-09-07T12:24:11.683+00:00

    @Cataster By Setting up a VPN to your specific Storage Account, the traffic will go through a secure tunnel as opposed to over the internet. Follow the instructions to setup VPN to access Azure Files from Windows.

    There is a You video which talks about How to mount Azure File Share using P2S VPN.
    Troubleshoot Azure Files problems in Windows (SMB)

    Additional information: After configuring the private endpoint of the Storage Account to utilize the correct VNET and subnet that was correlated to the Express Route, and editing the hostfile of the local machine, mounting had become successful. There also required a DNS Zone to be added, and once added, there were no further issues with mounting the file share.

    About Point-to-Site VPN

    How to configure Point to site connections

    Confirm the end-goal was to establish mounting a file share by utilizing an existing Express Route.
    Created a private endpoint with the same region as the V-Net and subnets that were required (Ex, Central US).
    Once private endpoint was created, edited the host file of the on-prem device to include the private IP of the new endpoint.
    Established a mount through File Explorer, utilizing the private IP address from the new endpoint.
    The next steps were that you were going to see DNS configurations to ensure that new users could easily route to the Private IP of the new endpoint, and let myself know of your progression from there, and if the case is needed to be closed or if we need to proceed with further assistance.

    If you still find any difficulties, please let me know I would like to work closer on the issue. Can you share the complete screenshot of the error message.

    Please let us know if you have any further queries. I’m happy to assist you further.

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.