Subtitles of the Movie

In this movie we will look at the various ports that FileMaker Server and Server Advanced uses. As we do that, I will indicate which ones need to be configured to allow remote access. These are the three main components of FileMaker Server and Server Advanced. There's the database engine, the web server, and the web publishing engine. The regular data ports used by FileMaker Server to let FileMaker Pro clients connect is Port 5003. That port is also the one that traffic between the web publishing engine and the database engine is running on. That port is officially assigned to FileMaker, Inc., so there should not be any conflicts with other services or applications. That port is also hard coded into FileMaker Server and that means you cannot change it. If you want to let remote FileMaker Pro users connect to the files hosted inside your network, then you need to open Port 5003 on your firewall and forward all traffic on that port to the internal IP address of your FileMaker Server. ODBC and JDBC clients connect to FileMaker Server Advanced on Port 2399. Web clients normally connect to the web server through Port 80, but you can certainly use any other ports. 591 is a friendly used alternative for FileMaker purposes. Different ports are used when SSL is involved, but all of this is configured in IAS on Windows or Apache on OS X and it has very little to do with setting up your FileMaker Server or Server Advanced, but since the FileMaker Web Server module is also on the web server internally for that machine and for communicating with the web publishing engine, FileMaker uses a set of ports in the 1608 to 1618 range. This whole top section of ports really only comes into play when you have the various parts of FileMaker Server and Server Advanced installed on different machines. If the web publishing engine, for instance, is not on the same machine as the web server, then Ports 16016 and 16018 need to be opened on the path between the two machines. Note that you cannot configure these ports; they are what they are. These are all the ports in use for data flowing to and from the clients. Another type of connection to FileMaker Server is the FileMaker Server Admin Console. The Server Admin Console connects to the database engine on Port 16000 for the start page. Once the Admin Console is up and running, it uses Port 16001 and 16004. Now, these ports can be used through a firewall with network address translation. However, for best security, I would suggest creating a VPN connection to your network, instead of opening these ports on your firewall. Alternatively, you can also make a Remote Desktop connection to the FileMaker Server or to any other machine inside the network and then use the server Admin Console from there. When we talked about not being able to change those ports or those ports being officially assigned to FileMaker, this is where you can check that. This is the institution that is responsible for ports assignments, so if you then go and check on this page for anything that has to do with FileMaker, we'll come across some of the ports that we've just discussed, such as 591, which is the HTTP alternative ports or, for instance, 2399, which is the ODBC and JDBC ports, or 5003, which is the regular port for traffic to and from FileMaker Pro clients. So, since these ports are assigned to FileMaker, there should not be any conflicts with any other services or applications.