We've got a FM solution that consists of a number of different files. They all have the same un/pw so you only enter it the first time and then the other files open without the need for credentials again.

I recently added a new file into the mix of things to store images pulled from a digital camera. I added the same un/pw to this file just like I did all of the others. I was actually working remotely and I logged into the FM server, added the new file and opened it up inside FM Server. It shows running just like the rest of them. From this point on everything worked great for me...remotely.

I come into the building today where the actual FM server is located and when I try and open the file that is related to the new CameraImports file but it hangs for a long time and gives me a message: "CameraImports.fp7 could not be opened. Either the host is not available, or the file is not available on that host."

I say OK to that and it gives me the open file dialog. I click Remote here and the CameraImports file shows up in the list just like it should an when I open it up it works just fine. doesn't ask for a pw either cuz the other files are already logged in and it's the same.

So again, this doesn't happen when I log in remotely from my house. It's only happening when using a local private IP address to connect to FM and only with this 1 file.

For example, at my house I use filemaker.ourdomain.com to connect to our FM files via Open Remote. In-house we use 192.168.1.*. Could that have anything to do with it? why would this only be happening when I use the local private address and not when I use the public address?

Any information would be greatly appreciated. Thanks!

Check the file references (Manage external data sources) in the files that point to your new file.

Make sure they look like this:

file:fileName

...and not like this:

fmnet:/IPaddress/fileName

that did it. thanks!