I am on my last wit! I am trying to get the web interface to work. I have one computer with Filemaker 5 Unlimited and the database networked to an active web server with W2K and IIS. I have loaded Filemaker 5 Unlimited, Java, Optigold and finally WSC. Optigold on the web server accesses the data fine. I have followed the instuctions, checked and rechecked, to no avail. Not only will http://localhost/menu.html:591 not respond, even the WDC Admin link created by loading WDC will not respond! My only guess is that, due to the boot drive being a non-default of D:, something is hard-coded looking for everything to be on a C: drive. All I get under any circumstances is the "404" message. The rest of the sites on this server all work fine. Can I get some suggestions on which way to go?
Does it work without the WSC? Best thing to do is get that working first, since that's required for WSC.
No, I tried and tried the first day without WSC even loaded. I thought maybe that was the problem, so I loaded it yesterday. The instructions in the manual are simple enough. How does IIS "know" to let FileMaker provide web services for these addresses? I have been assuming that is where the problem is, but I certainly do not know it to be true. Just shooting from the hip into the dark ...
OK. I removed WSC, Optigold, FM Unlimited, deleted remaining directories, then restarted server. I loaded FM Unlimited 5.0 to a different drive, then applied the .06 patch. Next loaded Optigold. Retstarted server. Then I started Optigold, logged in and updated the location for Web Security.fp5. Logged off, then back on as the web server employee. Then I activated the Web Companion, it complained about port 80 in use so I set it to port 591 as suggested. I insured that Instant Web Publishing wasn't enabled, set home page to index.html, enabled all logging and verified Web Security Database was selected. Saved that, went to Sharing and checked Web Companion as shared. Saved that. Then I opened the browser and entered http://localhost/index.html:591 and got a 404 error. I also tried http://dns2/index.html:591 and also got a 404 error. Is there some method to verify that Web Companion is actually working at all? Other than complaining about the port address, I do not know how to verify that it is functioning. All suggestions are welcome!
The above URLs won't work because the port needs to be after the host name (not the file). For example... http://localhost:591/index.html
Something about not seeing the forest for the trees ... That was it, can't believe that I did that. Can I trouble you with what I hope will be as simple? Seeing how this computer also is an IIS web server, what is your suggestion for making this available via the Internet? I thought I could simply make a shortcut folder in an already available web site, but that isn't working.
The only way to serve the pages through IIS would be to install WSC and do it that way (but at least the rest works for you now).
At least I get to see something besides "404!" Is it odd that only "localhost:591" works and not the machine name? I tried both "dns2:591" and the full name "dns2.syberwerx.net:591" but neither one works. I did load WSC, following along the instructions from the WSC PDF file, and have hit starting WSC Admin, which didn't. Getting smarter (only a little) I noticed that the link did not have the correct port, so I changed it to http://localhost:591/FMPro?config. In the Access log it shows 127.0.0.1 - - [11/Jun/2005:16:33:03 -0600] "GET /FMPro?config HTTP/1.1" 0 after submitting, but the brower only says "The page cannot be displayed."
I did determine the problem with using the actual machine name. As this is a live web server, we use IPSec policies and IP port filtering. Once I added port 591, the machine name worked. It did not, however, have any effect on WSC, nor did disabling IPSec policies. I am still hanging on getting the WSC Admin to actually display. I understand that WSC is not actually a part of Optigold, but everyone certainly has much more experience with it than I do! Suggestions?
I'm not sure to be honest. Whenever I've tried installed WSC myself, it's always "just worked". You may want to give FileMaker a call on that if it's not working.
I tried looking at FileMaker's FAQ, finally just gave up. It is easier for me to pull an old system out and use it as a dedicated web server. So that is what I did. And I almost got it all to working. With a clean XP Pro OS, no IIS, Filemaker is supposed to provide web services? It does work from the computer that it is loaded on, to include DNS name resolution, but it does not work from other computers' browers. Of course XP Pro SP2 now has a firewall, but I did exclude FileMaker Pro from it. I am burnt out for the day, can no longer think straight, so fresh start tomorrow.
It's always better when you get to answer your own questions! Web services are working fine. The problem has nothing to do with software and everything to do with hardware firewalls. Site works fine from the WAN side, but for some reason the firewall just won't accept that the server is on the DMZ and is killing all traffic to it from the LAN side. Keeps thinking that it is an IP Spoof. Well, I can tackle that in the morning, at least I can sleep better knowing that it is now working!