Azure file shares could not be accessed | Port 445Windows Azure Client with IP address 'XXX.XXX.XXX.XX' is not allowed to access the serverAccessing the file share from Azure Worker RoleAzure Point to Site port 445Not able to map drive to Azure File Storage share and port 445 openCan I mount Azure Files Storage from my local Workstation?Azure VM (ARM) external port not workingNot able to connect to Azure server using “NET USE <drive>…” commandCannot mount drive on-premises - Azure file storage over VPNOpening of the port in AzureNot able to connect to Azure File share drive, using Map drive its not connecting and I have added the port 445 too

Was "The Hobbit" ever abridged?

FORMAT returns large row size and data size

Where on Earth is it easiest to survive in the wilderness?

First Number to Contain Each Letter

How do I delete cookies from a specific site?

To which airspace does the border of two adjacent airspaces belong to?

Bidirectional Dictionary

Low quality postdoc application and deadline extension

Is there any reason to change the ISO manually?

Is mathematics truth?

ASCII Maze Rendering 3000

Is it possible to observe space debris with Binoculars?

MOSFET broke after attaching capacitor bank

Is the Levitate spell supposed to basically disable a melee-based enemy?

Numerical minimum of a one-valued function

What is the source of the fear in the Hallow spell's extra Fear effect?

Did the US Climate Reference Network Show No New Warming Since 2005 in the US?

Undefined Hamiltonian for this particular Lagrangian

Is using different public keys for different peers safer than reusing the public key, beyond forward secrecy - x25519

Is a paralyzed creature limp or rigid?

What drugs were used in England during the High Middle Ages?

How do I stop making people jump at home and at work?

How does the UK House of Commons think they can prolong the deadline of Brexit?

Professor refuses to write a recommendation letter to students who haven't written a research paper with him



Azure file shares could not be accessed | Port 445


Windows Azure Client with IP address 'XXX.XXX.XXX.XX' is not allowed to access the serverAccessing the file share from Azure Worker RoleAzure Point to Site port 445Not able to map drive to Azure File Storage share and port 445 openCan I mount Azure Files Storage from my local Workstation?Azure VM (ARM) external port not workingNot able to connect to Azure server using “NET USE <drive>…” commandCannot mount drive on-premises - Azure file storage over VPNOpening of the port in AzureNot able to connect to Azure File share drive, using Map drive its not connecting and I have added the port 445 too






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I have setup Azure Storage Files, I have added a couple of firewall rules in my dev machine to open the port#445. But I could not access my file shares now. It does not respond to ping command as well.



But I am able to access the same file shares from Azure VM IaaS Servers. Is there something I missed?










share|improve this question






























    0















    I have setup Azure Storage Files, I have added a couple of firewall rules in my dev machine to open the port#445. But I could not access my file shares now. It does not respond to ping command as well.



    But I am able to access the same file shares from Azure VM IaaS Servers. Is there something I missed?










    share|improve this question


























      0












      0








      0


      1






      I have setup Azure Storage Files, I have added a couple of firewall rules in my dev machine to open the port#445. But I could not access my file shares now. It does not respond to ping command as well.



      But I am able to access the same file shares from Azure VM IaaS Servers. Is there something I missed?










      share|improve this question














      I have setup Azure Storage Files, I have added a couple of firewall rules in my dev machine to open the port#445. But I could not access my file shares now. It does not respond to ping command as well.



      But I am able to access the same file shares from Azure VM IaaS Servers. Is there something I missed?







      azure azure-files






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 28 at 4:05









      Ashokan SivapragasamAshokan Sivapragasam

      7673 silver badges20 bronze badges




      7673 silver badges20 bronze badges

























          2 Answers
          2






          active

          oldest

          votes


















          1
















          It's not recommended to directly use PING command to verify network connectivity to a public DNS name or IP address as usually PING is forbidden. You could use PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to verify the port 445 on the dev machine.



          If this TCP 445 connectivity fails, properly you could check the ISP or your on-premise network security is not blocking outbound port 445. Please note that you should open outbound port instead of inbound port 445.



          As a test result, on my local machine, TCP test port 445 is false.
          enter image description here



          On the Azure VM, TCP test port 445 is true, and I could access the storage file share successfully.
          enter image description here



          Additionally, port 445 always is not allowed to access over the Internet. You could use different ways to access files in Azure Files.




          You can mount the file share on your local machine by using the SMB
          3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage
          client libraries, REST APIs, PowerShell, or Azure CLI to access your
          files in the Azure file share.







          share|improve this answer

























          • Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

            – Ashokan Sivapragasam
            Mar 28 at 6:58






          • 1





            Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

            – Nancy Xiong
            Mar 28 at 7:13



















          1
















          Refer to the suggestions mentioned in the GitHub article



          One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning



          Can you mount that drive from a VM in Azure, just to make sure it's not a problem with the file share? In fact, I'd try it from a VM in a different region if you can, which will confirm that SMB 3.0 is working correctly.



          Troubleshooter for Azure Files storage problems



          Kindly let us know if the above helps or you need further assistance on this issue.



          If the issue still persist,share the screen shot of the error message






          share|improve this answer

























          • We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

            – Ashokan Sivapragasam
            Mar 28 at 6:58













          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55389991%2fazure-file-shares-could-not-be-accessed-port-445%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1
















          It's not recommended to directly use PING command to verify network connectivity to a public DNS name or IP address as usually PING is forbidden. You could use PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to verify the port 445 on the dev machine.



          If this TCP 445 connectivity fails, properly you could check the ISP or your on-premise network security is not blocking outbound port 445. Please note that you should open outbound port instead of inbound port 445.



          As a test result, on my local machine, TCP test port 445 is false.
          enter image description here



          On the Azure VM, TCP test port 445 is true, and I could access the storage file share successfully.
          enter image description here



          Additionally, port 445 always is not allowed to access over the Internet. You could use different ways to access files in Azure Files.




          You can mount the file share on your local machine by using the SMB
          3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage
          client libraries, REST APIs, PowerShell, or Azure CLI to access your
          files in the Azure file share.







          share|improve this answer

























          • Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

            – Ashokan Sivapragasam
            Mar 28 at 6:58






          • 1





            Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

            – Nancy Xiong
            Mar 28 at 7:13
















          1
















          It's not recommended to directly use PING command to verify network connectivity to a public DNS name or IP address as usually PING is forbidden. You could use PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to verify the port 445 on the dev machine.



          If this TCP 445 connectivity fails, properly you could check the ISP or your on-premise network security is not blocking outbound port 445. Please note that you should open outbound port instead of inbound port 445.



          As a test result, on my local machine, TCP test port 445 is false.
          enter image description here



          On the Azure VM, TCP test port 445 is true, and I could access the storage file share successfully.
          enter image description here



          Additionally, port 445 always is not allowed to access over the Internet. You could use different ways to access files in Azure Files.




          You can mount the file share on your local machine by using the SMB
          3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage
          client libraries, REST APIs, PowerShell, or Azure CLI to access your
          files in the Azure file share.







          share|improve this answer

























          • Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

            – Ashokan Sivapragasam
            Mar 28 at 6:58






          • 1





            Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

            – Nancy Xiong
            Mar 28 at 7:13














          1














          1










          1









          It's not recommended to directly use PING command to verify network connectivity to a public DNS name or IP address as usually PING is forbidden. You could use PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to verify the port 445 on the dev machine.



          If this TCP 445 connectivity fails, properly you could check the ISP or your on-premise network security is not blocking outbound port 445. Please note that you should open outbound port instead of inbound port 445.



          As a test result, on my local machine, TCP test port 445 is false.
          enter image description here



          On the Azure VM, TCP test port 445 is true, and I could access the storage file share successfully.
          enter image description here



          Additionally, port 445 always is not allowed to access over the Internet. You could use different ways to access files in Azure Files.




          You can mount the file share on your local machine by using the SMB
          3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage
          client libraries, REST APIs, PowerShell, or Azure CLI to access your
          files in the Azure file share.







          share|improve this answer













          It's not recommended to directly use PING command to verify network connectivity to a public DNS name or IP address as usually PING is forbidden. You could use PowerShell command Test-NetConnection -Port 445 -ComputerName somestoragexxx.file.core.windows.net to verify the port 445 on the dev machine.



          If this TCP 445 connectivity fails, properly you could check the ISP or your on-premise network security is not blocking outbound port 445. Please note that you should open outbound port instead of inbound port 445.



          As a test result, on my local machine, TCP test port 445 is false.
          enter image description here



          On the Azure VM, TCP test port 445 is true, and I could access the storage file share successfully.
          enter image description here



          Additionally, port 445 always is not allowed to access over the Internet. You could use different ways to access files in Azure Files.




          You can mount the file share on your local machine by using the SMB
          3.0 protocol, or you can use tools like Storage Explorer to access files in your file share. From your application, you can use storage
          client libraries, REST APIs, PowerShell, or Azure CLI to access your
          files in the Azure file share.








          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 28 at 6:25









          Nancy XiongNancy Xiong

          7,0551 gold badge2 silver badges11 bronze badges




          7,0551 gold badge2 silver badges11 bronze badges















          • Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

            – Ashokan Sivapragasam
            Mar 28 at 6:58






          • 1





            Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

            – Nancy Xiong
            Mar 28 at 7:13


















          • Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

            – Ashokan Sivapragasam
            Mar 28 at 6:58






          • 1





            Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

            – Nancy Xiong
            Mar 28 at 7:13

















          Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

          – Ashokan Sivapragasam
          Mar 28 at 6:58





          Test-NetConnection returns true for my file share. But it does not map in my local machine. Should I assume that it is due to on-premise organization firewall blocking it? But it always works well in any Azure VM.

          – Ashokan Sivapragasam
          Mar 28 at 6:58




          1




          1





          Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

          – Nancy Xiong
          Mar 28 at 7:13






          Organization firewall or Internet service provider security. By default, Azure VM locally traffic goes to the Internet without limitation as well as NSG. Also, Azure routes traffic for any address not specified by an address range within a virtual network, to the Internet, with one exception. If the destination address is for one of Azure's services, Azure routes the traffic directly to the service over Azure's backbone network, rather than routing the traffic to the Internet. refer to this.

          – Nancy Xiong
          Mar 28 at 7:13














          1
















          Refer to the suggestions mentioned in the GitHub article



          One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning



          Can you mount that drive from a VM in Azure, just to make sure it's not a problem with the file share? In fact, I'd try it from a VM in a different region if you can, which will confirm that SMB 3.0 is working correctly.



          Troubleshooter for Azure Files storage problems



          Kindly let us know if the above helps or you need further assistance on this issue.



          If the issue still persist,share the screen shot of the error message






          share|improve this answer

























          • We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

            – Ashokan Sivapragasam
            Mar 28 at 6:58















          1
















          Refer to the suggestions mentioned in the GitHub article



          One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning



          Can you mount that drive from a VM in Azure, just to make sure it's not a problem with the file share? In fact, I'd try it from a VM in a different region if you can, which will confirm that SMB 3.0 is working correctly.



          Troubleshooter for Azure Files storage problems



          Kindly let us know if the above helps or you need further assistance on this issue.



          If the issue still persist,share the screen shot of the error message






          share|improve this answer

























          • We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

            – Ashokan Sivapragasam
            Mar 28 at 6:58













          1














          1










          1









          Refer to the suggestions mentioned in the GitHub article



          One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning



          Can you mount that drive from a VM in Azure, just to make sure it's not a problem with the file share? In fact, I'd try it from a VM in a different region if you can, which will confirm that SMB 3.0 is working correctly.



          Troubleshooter for Azure Files storage problems



          Kindly let us know if the above helps or you need further assistance on this issue.



          If the issue still persist,share the screen shot of the error message






          share|improve this answer













          Refer to the suggestions mentioned in the GitHub article



          One alternative to mounting the share on-premises over port 445 is Azure File Sync, which enables you to create a cache of an Azure file share on an on-premises Windows Server. Azure File Sync only sends data over the Azure Files HTTPS (using the File REST APIs). You can learn more about Azure File Sync here: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning



          Can you mount that drive from a VM in Azure, just to make sure it's not a problem with the file share? In fact, I'd try it from a VM in a different region if you can, which will confirm that SMB 3.0 is working correctly.



          Troubleshooter for Azure Files storage problems



          Kindly let us know if the above helps or you need further assistance on this issue.



          If the issue still persist,share the screen shot of the error message







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 28 at 6:12









          SumanthMarigowda-MSFTSumanthMarigowda-MSFT

          7693 silver badges7 bronze badges




          7693 silver badges7 bronze badges















          • We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

            – Ashokan Sivapragasam
            Mar 28 at 6:58

















          • We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

            – Ashokan Sivapragasam
            Mar 28 at 6:58
















          We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

          – Ashokan Sivapragasam
          Mar 28 at 6:58





          We are working on Azure File Sync as well. It is nice. Thanks for recommendations!

          – Ashokan Sivapragasam
          Mar 28 at 6:58

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55389991%2fazure-file-shares-could-not-be-accessed-port-445%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

          Swift 4 - func physicsWorld not invoked on collision? The Next CEO of Stack OverflowHow to call Objective-C code from Swift#ifdef replacement in the Swift language@selector() in Swift?#pragma mark in Swift?Swift for loop: for index, element in array?dispatch_after - GCD in Swift?Swift Beta performance: sorting arraysSplit a String into an array in Swift?The use of Swift 3 @objc inference in Swift 4 mode is deprecated?How to optimize UITableViewCell, because my UITableView lags

          Access current req object everywhere in Node.js ExpressWhy are global variables considered bad practice? (node.js)Using req & res across functionsHow do I get the path to the current script with Node.js?What is Node.js' Connect, Express and “middleware”?Node.js w/ express error handling in callbackHow to access the GET parameters after “?” in Express?Modify Node.js req object parametersAccess “app” variable inside of ExpressJS/ConnectJS middleware?Node.js Express app - request objectAngular Http Module considered middleware?Session variables in ExpressJSAdd properties to the req object in expressjs with Typescript