Newbies MazdaBoi Posted November 2, 2001 Newbies Share Posted November 2, 2001 Hello all. I'm a novice with FileMaker Pro... I am a MySQL nut, personally... But I'm having some problems with a database machine at my workplace. It's FileMaker Pro 4.0 running on MacOS. For the past week or so, the web interface to the database has been dying for no apparent reason. The GUI on the Mac itself continues to work just fine... To revive the web interface, I have to shut FM down, and restart it. The web interface will be fine for about 15 minutes, then it will die again.... Has anyone ever seen this behavior? If so, do you happen to know any fixes for the problem? Thank you in advance for any advise Brad Link to comment Share on other sites More sharing options...
Anatoli Posted November 2, 2001 Share Posted November 2, 2001 It can be anything on that machine. Possibly the TCP/IP settings or some problem. Link to comment Share on other sites More sharing options...
Anatoli Posted November 3, 2001 Share Posted November 3, 2001 What is the meaning of "the web interface to the database has been dying“? Link to comment Share on other sites More sharing options...
Newbies MazdaBoi Posted November 3, 2001 Author Newbies Share Posted November 3, 2001 I think it's called the Web Companion? FileMaker's GUI on the mac continues to work perfect, as if nothing happened. The Web Companion ceases to accept connections at all... The port isn't even open on the machine.... Link to comment Share on other sites More sharing options...
dwal Posted November 5, 2001 Share Posted November 5, 2001 Both 'Code Red' and 'Nimda' can disable Web Companion on Mac. On our server it can happen in about 20 minutes after restarting the computer. These worms may be able to do this by not allowing the TCP/IP connection to close and in the case of 'Code Red' it may cause a buffer overflow. A single threaded sever such as Web Companion in FMP Unlimited 5.0 can be disabled if the connection is not allowed to close. You can read more about this at http://www.sustainablesoftworks.com. I have ended the problem for our server by using their IPNet Sentry. You will need to configure the triggers to block all types of 'Nimda' packets. I believe there are about six. Also it is important to set the trigger to close the connection. If you do not then I have found the connection does not close and web companion stops serving. Go to http://www.sustainablesoftworks.com/site/net_sentry/command_syntax_document.htm to see an example. It is about half way down the page. Link to comment Share on other sites More sharing options...
Newbies MazdaBoi Posted November 5, 2001 Author Newbies Share Posted November 5, 2001 Interesting... I turned up the logging to see what's going on... Hopefully I'll have an answer soon... Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 8206 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now