I am trying to set up FileMaker Server on a new Azure Windows 2012 VM (not classic).
The step that has me flummoxed is opening the ports. I have created the inbound end points for the three required ports in the Azure console and created the 3 inbound rules in the windows firewall.
Two of the ports, 180 and 1443 seem to be open, verified with an online port tester. However 16001, which is the most important one to get started is not open. I double and triple checked everything and the three rules are identical except for the port number.
For the heck of it (and because I thought maybe there was a problem with higher numbered ports? - grasping at straws here) I randomly tried opening port 181. Did not work.
I can connect to FileMaker Server using port 16001 locally so I at least know it's operational. But, I can't make any external connections to the FileMaker Server.
Learned a new trick and ran a NetStat on my server for each port. Here is a screenshot.
The two that are working, 180 and 1443 are using 0.0.0.0 and the two that aren't working are using 127.0.0.1 and 10.0.0.4. I partially understand the difference between 0.0.0.0 and 127.0.0.1 in this context and explains why 16001 is not working. But where did 10.0.0.4 come from?
And how do I change everything to use 0.0.0.0? Apparently not in Windows Firewall where the configurations are identical.