That’s it! You should be able to connect via FileMaker/Go and also to the Admin Console from outside the server. On the final page of the wizard, simply name the inbound firewall rule and click Finish.Since these ports are only going to be used for FMserver, it’s OK to leave them all checked: The next screen of the wizard is called the “Profile” screen.On the next screen, choose “Allow the Connection” and click Next.On the “Protocols and Ports” page of the wizard, choose “TCP” and add the necessary ports separated by commas:.In the “New Inbound Rule Wizard, click on the “Port” options.Next, click on the “New Rule” link in the right sidebar:.Click on the “Inbound Rules” link in the left sidebar at the top.The Windows firewall dialog window will open.Click on “Windows Firewall with Advanced Security”.Depending on the version of Windows Server you have, you should see something like this:.Press the Windows key plus the S key to open Windows search (Win+S) (if you’re on Win 2008, click the start button and search from there).I’ve even seen recommendations to simply turn off Windows Server firewall in AWS, but this is not necessary if we understand a few nuances about Windows Server firewall. There seems to be a lot of confusion about how to use Windows Server firewall especially in VMs like on Amazon Web Services or Azure. Why: Instead of disabling the firewall, let’s learn to use it!.With: FileMaker Server 13+ / Windows Server 2008+.What: How to Configure Windows Server Firewall for FileMaker Server.Who: All Users setting up FileMaker Server on a Windows Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |