Troubleshooting : Network problems
 
Network problems
Note  The following information is for server administrators.
A FileMaker Pro client using TCP/IP can't find FileMaker Server databases on the network
Verify that TCP/IP networking software is properly configured on the host and client computers. Verify that the simultaneous client limit you specified has not been reached.
FileMaker Pro databases shared via TCP/IP can be opened remotely using the list of local hosts, the IP address of the host machine, or the DNS name of the host machine if one has been defined. For example, a database hosted from a computer with an IP address of 192.168.10.0, and a DNS name of host.domain.com can be opened by entering either the IP address or the DNS name in the Network Path dialog box, using the format fmnet:/192.168.10.0/<filename>. (Note that fmnet:/ uses a single slash.)
Note  FileMaker Pro also supports IPv6 addresses in the form of eight four-digit number groups, separated by colons and surrounded by square brackets ([]). For example, fmnet:/[2001:0DB8:85A3:08D3:1319:8A2E:0370:7334]/<filename>
If no FileMaker Pro client computers can see FileMaker Server in the Launch Center, check the server network connection, and make sure the FileMaker Server ports are open on any firewall.
Cannot start Admin Console from a remote machine
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 Ports used by FileMaker Server.
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 from the FileMaker Server Admin Console page again. See Starting Admin Console.
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 Ports used by FileMaker Server for information on which ports need to be unblocked in firewalls.
Clients cannot access the FileMaker WebDirect Launch Center
Verify that the clients are specifying the correct IP address or domain name for the machine running the web server component. For a two-machine deployment, the worker machine runs the web server component.
If you use SSL database connections, clients must use the fully qualified domain name instead of the IP address.
For a two-machine deployment, if you make network configuration changes, changes to the domain name, or changes to the SSL certificate on the worker machine, you must redeploy. See Changing a FileMaker Server deployment.
Related topics 
FileMaker Server event log messages
Troubleshooting