Installation guide

40 FileMaker Server Getting Started Guide
Admin Console Start Page says to install Java when it’s already installed
Internet Explorer may be configured to prevent add-ons from running. Click the Information Bar at the top
of the browser window and allow Internet Explorer to run the Java Web Start ActiveX Control add-on. Java
Web Start technology uses this add-on to detect whether the required version of Java is installed. After you
allow this add-on to run, click Start Admin Console.
Cannot start Admin Console from a remote machine
1 If the master machine has a firewall enabled, then you must open the ports required by FileMaker Server
to communicate with users and administrators. See
“Before you begin” on page 25.
1 If you double-click an Admin Console shortcut and Admin Console doesn’t open, check whether the IP
address of the master machine has changed. Each shortcut starts Admin Console for a specific FileMaker
Server deployment. If the IP address of the master machine has changed, you must remove the shortcut
and start Admin Console again. See
“Starting Admin Console” on page 43.
Clients cannot see databases hosted by FileMaker Server
The firewall settings on the master machine may be blocking the display of databases to clients. See “Before
you begin” on page 13 and “Before you begin” on page 25 for more information on which ports need to be
unblocked in firewalls.
The Mac OS web server fails during startup
When you install the FileMaker Server supported PHP engine, it does not appear in the Mac OS X Server
Admin tool; it is not supposed to be listed. If you use the Mac OS X Server Admin tool to turn on PHP, the
Server Admin tool adds a second PHP engine to the web server's configuration files. As a result, the web
server may fail during startup when it attempts to load the second PHP engine. Refer to the Knowledge Base
for more information.