|
|
|||
TITLE
|
|
||
TOPIC
Using the single-link multihoming (multinode) capability provided by Open Transport, I am hosting several websites (each with unique IP addresses) from my AppleShare IP 6.1 server. Most of these sites are served through AppleShare IP's Web Services, but one site is served with Filemaker Pro 4.1 Web Companion. I have set up MacDNS to include zone files for each site, and I have entered my IP addresses in the Secondary IP Addresses file in my System Folder. However, it appears as if the two services are fighting with each other: if Filemaker starts first, Web and File Services will not start, and if Web and File Services starts first, my Filemaker site cannot be accessed. How can I get these two applications to co-exist peacefully?
DISCUSSION
When setting up AppleShare IP Web Services in conjunction with a Filemaker Pro Web Companion database, administrators may run into a situation in which the two services prevent each other from operating as expected. The solution is to assign FileMaker Web Companion a different port than that which is typically reserved for http services.
Both Filemaker Pro Web Companion and AppleShare IP Web Services use TCP/IP port 80 by default. Therefore, you must assign a new port to Filemaker Pro. Although any unused port will suffice, your first choice should be port 591, as Filemaker, Inc. has registered this port with the Internet Assigned Numbers Authority for use with Web Companion. See Figure 1.
Figure 1: FileMaker Pro Web Companion Configuration window.
After you have changed this port, the IP address by which the site can be accessed will now be followed by a colon and the port number. For example:
your.website.com:591
In order to save visitors to your site the inconvenience of having to type in the port number, you should then create an HTML document at the top of the website folder served by Filemaker Web Companion with a hyperlink to your database.