Problem getting FMAS10 to be visible on public internet

[wngiii]

Hi. I'm having issues getting our FileMaker 10 Advnaced visible on the public Internet.

The documetion is a bit "light" on what needs to be moved/copied from where to get this working. Here's the background.

We have IWP running, with no problems, on our internal network. This is on IIS, Server 2k3.

I have mapped a public url and IP to point to a dedicated IP address, and setup the firewall to forward and NAT translate the public IP address to the private internal IP address. DNS entries are configured so that the same url works both internally and externally. The internal DNS entry points to the internal IP address of the server, 10.1.1.155, and the public IP address gets NAT'ed to the same internal IP address.

Initially, when I got this setup, from INSIDE I got the IWP home page, listing the shared database you can click on, then get to the FM login screen. Good.

When coming around from the PUBLiC side, I get the IIS Under Construction page, and no resolve to the IWP home page.

Initial thought, was I needed a "landing" page, so I added a default.htm page, that has the LINK to the internal database.

That got me similar results. From inside, I now get the default.htm landing page, with a working link to the IWP home page.

From the PUBLIC side, I get the same default.htm landing page, but the link to the DB doesn't work.

From reading the docs, there is discussion about MOVING file from a "Web" folder to the iisroot folder (which would be the IIS Default site), but looking at the FMServer 10 directory structure, I'm not really sure WHAT files from where need to be moved/copied to get all of this functioning properly.

Any pointer/help would be VERY appreciated.

We're trying to get this site active for demonstration next week some time, and I'm SURE it's an easy fix.

[Wim Decorte]

Since it is working internally but not externally it must be something in the firewall/router and the mapping.

Unless you defined some access rules in the IIS manager.

Are you using the default port 80?

There is absolutely no need to move any of the FM files.

[Steven H. Blackwell]

In the IIS Manager be sure you have set authentication to be anonymous access only.

Steven

[wngiii]

OK, I think I've figured out what I'm missing. No re-direct in place!!!

If I remove the default.htm simple landing page I created, then I now get the "Under Construction" default IIS error page both from inside and out.

Re-reading everything, I've MISSED adding a redirect to http:///fmi/iwp. The QUESTION is WHERE is that added? When looking at the IIS setup, there is a "jakarta" entry, that points to the isappi.dll, there is the mf-test entry. Do I create a new "Virtual Directly", and then point that to "another website on this computer", putting in the http:///fmi/iwp entry mentioned in the docs?

What we've been using internally is a long url, that goes as follows:

http://sv10-idb/fmi/iwp/res/iwp_home.html where sv10-idb is the name of the server. I've got a DNS entry that resolves to that server using the name db1..

Pointers here I think will finally resolve this issie.

Thanks to all for you pointers/help, as the docs are not fully clear on this one.

Oh, and this is NOT on XP as the platform, it's on Windows 2k3 server, full IIS installed.

Edited February 14, 2010 by Guest

[wngiii]

Just an aside, the FW has been confirmed to be working, so it's a matter of what/where/how to get the proper re-direct in place I believe.

I can now connect to the DB internally using the following url:

http://db1.indieblu.com/fmi/iwp

What I really want to do, is NOT have to use the /fmi/iwp at the end of the url, and have the redirect place the web call in the proper place. i've been unsuccessful at doing that, at this point.

wng

[siuts]

Hi-

I could do that with WinSvr 2003, IIS 6 and Filemaker Server Advanced 9.

In IIS services manager, I made a second web site that was the domain name of the filemaker server. Then I right clicked it and went to properties. In the Home Directory tab, I left everything the default except "The content for this resource should come from:" and there I choose A redirection to a URL and entered "http://theServerIP#/fmi/iwp/cgi.

I think that is the only change I made. My end users were able to enter the registered domain name of the filemaker server into a browser address bar and get to their databases from any office.

Now I'm trying to do the same thing with Filemaker Server Advanced 10, Win Server 2008 R2 and IIS 7.5. I can't find the corresponding settings in the new configuration.