I am moving our companies filemaker DB to an external host to speed up access from our rails app. I work remotely and can connect with filemaker and open the db. However from within the office filemaker cannot connect. I get the server not available dialog. Is there any reason that I shouldn't be able to connect? I have tried a url and the ip address and neither work... There is no firewalls on the client machines... Suggestions?

There is no firewalls on the client machines...

But is there a firewall on the router/gateway?

Of course. But it isn't setup to stop outgoing requests and should open up a connection to the server for the requesting computer. It has an identical setup that I am using at my house which works. What port does fm connect to a server on? Could an ISP for some reason block that port? I have also used a neighbouring wi-fi connection with the same result. The ISP is AT&T in both cases.

FM runs on port 5003 for native FMP connections.

GRRRRR!? Come on! SSL certificate updater needed to be applied. Why oh why did that take two days to figure out. Could they have built in a little bit better error message than a generic meaningless one? Hopefully this helps someone.

Sorry, I did know about that, however your info shows FM 7, whereas SSL updater only became a problem with FM 9

No need to apologize. Its not your fault. I appreciate all of the help you gave me. My problem is with how filemaker handles this type of error. If they are going to release an update that breaks there app, might be nice to know about. Would be easy enough to display an error that provides some useful information pointing to a fix.

I don't update my info regarding what version of fm I use because I use several versions. However, I should have posted it with my question. Lesson learned.

Thanks again for your help,

Larry