From e640bf70f11eeb998fb5bbb33d919033581f4e1d Mon Sep 17 00:00:00 2001 From: Cesar De la Torre Date: Wed, 10 May 2017 14:43:47 -0700 Subject: [PATCH] Updated 02. Setting eShopOnContainer solution up in a Visual Studio 2017 environment (markdown) --- ...Container-solution-up-in-a-Visual-Studio-2017-environment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md index 5102fd8..e9d45c4 100644 --- a/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md +++ b/02.-Setting-eShopOnContainer-solution-up-in-a-Visual-Studio-2017-environment.md @@ -68,7 +68,7 @@ https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-w ### IMPORTANT: Open ports in local Firewall so Authentication to the STS (Security Token Service container) can be done through the 10.0.75.1 IP which should be available and already setup by Docker. Also needed for client remote apps like Xamarin app or SPA app in remote browser. - You can manually create a rule in your local firewall in your development machine or you can also create that rule by just executing the add-firewall-docker.ps1 script available in the solution's **cli-windows** folder. -- Basically, you need to open the ports 5100 to 5105 that are used by the solution by creating an IN-BOUND RULE in your firewall, as shown in the screenshot below (for Windows). +- Basically, you need to open the ports 5100 to 5110 that are used by the solution by creating an IN-BOUND RULE in your firewall, as shown in the screenshot below (for Windows).