paint me stupid, but you've added the ports list to your firewall right? I have little to no experience with mac servers, and the mavericks release made that worse. But if you compare to the windows server counterpart, only the ports are required in the firewall, not the program itself.
According to the "official" documentation:
that should be all that is needed. Ports 80, 5003, 16000 and optionally 443 and 2399
What portion of FMS gets blocked if you have those ports in the whitelist? (at this point I'm wondering for my own education, sorry I don't have a solution).
I think that the OS X firewall GUI is application based instead of port based these days. Changed with 10.6? I believe that it still has multiple firewall programs due to its UNIX base.
I seem to recall reading quite some time ago an article that talked about how to enable/use the older style firewall (IPFW). Do some searching in google/bing. A couple of quick hits I found.
There are 3rd party apps available as well.
Do a search for NoobProof and WaterRoof. I think these might provide a GUI for the IPFW firewall.
^ BowdenData is correct... The OS X Mav firewall is 'application' based (I sense that this type of behavior is indicative of all Mac apps being sandboxed in the future)... any and all ports the approved application wants to use will be allowed... and if another, unapproved application uses those ports, it won't be allowed.
Tim, Doug, I believe you are correct that the firewall is application based. The question, is what file/application do I add to the firewall to allow access to FMS? At the moment the solution is to simply turn the firewall off.
Well I made some progress with this. I added all of the available files in the folder /Library/FileMaker Server/Database Server/bin
This allowed FileMaker Pro to open a database on the server. However, WebDirect, Admin console and Uploading a new database still are not functional. I tried several other folders in the /Library/FileMaker Server/ hierarchy, but wasn't able to find the correct one for the Webserver. I think this is the next piece I have to find and add to the list of available files in the Firewall.
That's the hard part because there are likely many apps/processes involved in the equation with FM Server. This is why I gave a couple of links in my previous post about using the IPFW firewall that exists in OS X, instead of the "Application" one that Apple exposes in the System Preferences.
Just to reiterate in case it was not clear before, OSX has more than one firewall program built in. The simple, application based one that you are trying to use and the more traditional (port based), and configurable, IPFW program.
Based on your testing and no one being able to supply the solution, I would abandon the use of the application firewall and use the IPFW one instead. It can be configured through the Terminal, or as suggested, look at some of the 3rd party tools that provide a GUI for it. There are probably other tools beyond the couple that I found. I just did a very brief search.
1 of 1 people found this helpful
Having messed about trying to get the port based firewall to work we reluctantly tried the builtin application firewall. Installing FMS after the firewall was on and ticking the firewall option of 'automatically allow signed software to receive incoming connections' just worked. we got the prompt to allow the FMS ODBC driver to receive connections but otherwise no issues. I just wish we'd tried this first instead of wasting time configuring the ports - we added everything filemaker document but still couldn't get everything to work..
So... If I uninstall FMS, turn the firewall on and check the option of automaticly allow. I should be able to get this going? I'll try it.
We spent so long and tried so many things that I can't be absolutely sure, but I do believe that this is what worked for us.