Here's my trouble, I've got a FMWSC (from Unlimited 5) running on Mac OS X Server v1.2 via Apache. I've got several machines attached to this WSC, some Win 2000 PCs, an OS 9 Mac, and an OS X Mac...

One of my PCs (a 1.4Ghz P4 w 256 Megs of Ram running Unlimited 5 and W2k Pro) tends to crash quite frequently (sometimes FMP will just quit...) anyway if it's down for too long (I'm guessing more than a couple of hours - I haven't timed it) The Web Server Connector looses the entry for that machine.

So I can have someone on-site reboot the P4 and get the DB up, but it's still no use to my Web customers as the WSC doesn't know it's back up and running.

Does anyone know of a way to "Force" WSC to remember it's DB/IP/Port settings?

( possibly a unix file hack? ) - (is there a file that holds this info? )

-Arin

I wish there was an icon for a little face puking!

It just did it again... and this time I don't think the P4 machine crashed first...

It's so strange, I've got another PC running Win2000 and FMP Unlimited 5 that this NEVER happens to... The one that works is a 1.3Ghz AMD Athlon machine with 1G of 266DDR Ram, and a 10/100 Netgear PCI ethernet card...

The one that keeps disconnecting is a Dell P4 1.4Ghz with 256Megs of 266 DDR Ram, and a Dell provided 10/100 Ethernet card... is it possibel that the network connection is just crappy?

Either way (Hardware or Software issue) I'd still like to know how to force WSC to remember the IP...

-a

Our WSC frequently forgets the connection to own machine -- everything is running on single box. WSC is useful in it's designed functionality, but works unreliably.

Best practice is to leave the configuration HTML page open and post the settings again.

I find that using a machine just for Fm WSC only on it works the best.

I had mine on my web server and it was very unreliable.

But with it on a seperate machine I have had no problems since I made the switch.

Well, the WSC is plugin to the IIS, so on Windows it must be on the same machine. Am I wrong?