I have been supporting a company running Filemaker Server and about 15 clients for quite a few years through various version upgrades. I have never previously had a problem with the clients seeing the host files. I upgraded the Mac OS and Filemaker versions about 6 weeks ago and initially every client computer was able to connect with no issues, but now there are three clients that can't connect. I have eliminated any possible problems before the Client machines and checked that the correct ports are open from those machines, I have run diagnostic tests on the OS, updated it to 15.5 and reinstalled FMP but the problem persists. Today I tried installing FMP on my personal MacBook, also running 15.5, and had no problems connecting immediately. I haven't been able so far to find any reports of the problem online so would appreciate any advice. I haven't yet tried an OS reinstall but it seems strange that three machines all have an OS problem. Grateful for any help!

in server there is a setting to filter databases. The user may need to authenticate first to see the list of files. 

Alternatively on all computers and server you can enable HTTPS tunneling and then you will no longer need to have 5003 open on your router. 


 

Thanks, I'll check that out

I have the same issue on 'certain' Sequoia computers. They will connect fine, then after connection via a different network or network blip, they cannot see hosted files. (And if they go from external network to internal network.)

Short term, I have to:  Remove permitted hosts, Quit FM, Log out of computer user account (don't have to restart computer), Launch FM, then Go to Hosts > Always allow > and they are able to see hosted Files again.

And it's ONLY on SOME Sequoia computers. I haven't been able to find the trigger or setting that causes this.

There's nothing in common with these computers except Sequoia. One's a laptop that moves in and out of the internal network, the other is a static desktop. Doesn't happen with any other OS flavors.

I am not familiar with https tunneling, it isn't enabled on the server, so I don't know if it would help.

Thanks, yes it's only 3 machines that are affected and that were connecting ok before.

I'll try your solution.

I now know the problem, after another suggestion.

Following a recent upgrade to OS 15, Filemaker started asking for local network access when first launched, some people must have clicked No rather than Yes which locked Filemaker out. Re-enabling Local Network access in Privacy & Security has fixed it.

So I found a reliable solution.   Despite the fact that my DNS resolves correctly,  and over 80 Macs work just fine,  just the odd one or two that won't,  I found the solution for me was to simple add an entry in the Mac's HOSTS file for the server.   A bit like this in terminal:

Log in as a user with sudoer privileges.

cd /private/etc

sudo pico hosts

add a line that is the IP address followed by the hostname that FileMaker isn't working with,  in my case something like this

192.168.111.202<tab>FileMaker.mydomainname.com

Don't type "<tab>" literally, press the TAB key!

Write out the changes.   No reboot, nothing.  The Mac that wouldn't work will now work.    You can add more lines if you have more than one FMS.

Regards

Ian Summerfield