Comments on: Configuring Firewall Ports for FileMaker 9

By: Herminia Ruberte

Herminia Ruberte — Thu, 06 Oct 2011 19:47:51 +0000

Helpful information. Lucky me I discovered your site by chance, and I’m stunned why this twist of fate did not took place in advance! I bookmarked it.

By: Stephane

Stephane — Tue, 23 Nov 2010 17:32:05 +0000

On our windows server 2003 with FMS 11, we had two crashes of Bonjour service (2.0.0). When it occurs, everybody loses their connections with the server. Very strange. Event log reports “428: ERROR: read_msg errno 10054 (An existing connection was forcibly closed by the remote host.)” Still looking for an explanation.

By: Rick Davis

Rick Davis — Tue, 26 Oct 2010 18:09:45 +0000

Shouldn’t the ports under web data read 16004 – 16007 instead of 16004 – 1607 Notice the missing 0.

By: Kevin

Kevin — Fri, 10 Sep 2010 10:08:07 +0000

I am still having problems with filemaker client seeing server on local host but can see server if server IP address is added under favourite hosts. I have added ports 5003 and 5353 on client firewall.

On server (FMS 11 running ) the firewall is set to allow bonjour and ports 5353 are also open. Connection between client and server machine does not go through a router. The thing is it was working fine. The server was switched off and moved to a different location in the office and when switched back on the local host discovery on the client no longer showed available files.

Is there anything else I can check to cure this strange error?

By: Andreas

Andreas — Thu, 29 Jul 2010 11:02:19 +0000

Hi,

Is there a solution for discovering the FM Server on an other subnet/vlan?
Something like the “ip helper address” for forwarding dhcp requests to an dhcp server on an other subnet/vlan.
Due to changes in the network i have my FM Server on an other subnet/vlan and now the clients can’t start there FM programs because they can’t find the server. When pointing to the server it works because i opened tcp/5003 but it’s so much code that i rather come up with a network or server side solution than changing it everywhere.

Thanks,

Andreas.

By: Philippe Lazzaroni

Philippe Lazzaroni — Sat, 05 Jun 2010 10:01:41 +0000

Hi Geoff

I’ve heard there were some minors changes brought to the network ports with the release of FileMaker Server 11. Let me know if you update the diagram so I can update the French version as well.

Thanks

Philippe

By: Ray

Ray — Sun, 20 Dec 2009 04:33:05 +0000

Great diagram! This is probably pretty obvious to most, but I wanted to point out some typos with regard to some of the ports (let me know if I’m mistaken): under the “Web Publishing Engine” entity you’ve listed ports “16004-1607″ and “1608-16018″. I believe those should be “16004-16007″ and “16008-16018″. Thanks!

By: Chue

Chue — Thu, 26 Feb 2009 21:44:46 +0000

good thing i found this post. helped me out a lot with the explanations. i have a current problem pertaining to firewalls. we have an xserve running 10.5 server and fms 9. our server firewall has all the appropriate ports enabled. my problem came about because the school campus where we are located recently implemented a new security policy (border firewall). i think they closed many of the ports that filemaker uses and outside connection ceased. from the outside through VPN, i can get to the the iwp. through VPN, using a filemaker pro client, i cannot see the server.

we also have tons of people logging into the server through iwp that are not tech savvy enough to download and install the vpn client. we are asking the campus security folks to open 5003 to see if this clears it up. i thought that having 80 open would resolve this? i don’t know too much about firewalls but boy am i learning fast. any advice on what i should ask/request of the campus security folks?

By: Haim Roman

Haim Roman — Sun, 15 Feb 2009 07:51:30 +0000

No where do you specify whether the protocol is TCP or UDP. I’m trying now to configure our firewall for this, so this is important. I’m assuming everything is TCP, except port 5353 (mutlicast DNS, or host discovery). According to the multicast DNS draft (http://files.multicastdns.org/draft-cheshire-dnsext-multicastdns.txt), it seems that it’s UDP. I’m adding both protocols, but this should be mentioned.

By: sebman

sebman — Mon, 26 Jan 2009 13:57:54 +0000

ehm – i think there is a small typo:
On the Server Side, between “Web publishing Engine” and “Web Server” shouldn’t it be:
Web Data 16000, 16004-16007 (not 1607), and 16008 (not 1608) -16018…

btw: Nice Work – makes a lot clearer to me now!