I've just installed FM10 onto a Win7 machine but our DBs aren't available in remote files. They are server using FMS9 Adv.

Is this supported, or do I need to upgrade to FMS10?

Thanks

Did you try to specify the host by its IP address? I know FileMaker on Windows wont discover any hosts without Bonjour being installed and active. If you don't want to install Bonjour you will have to specify the host machine.

Yes I did. I can see the host, but not the served files. Typing in the path gives a "host not available' dialogue.

I've checked Windows Firewall isn't the problem as well.

Bonjour is installed.

Edited February 10, 201015 yr by Guest

What's turned on at the Server? Encryption, external authentication, database visibility??

Be sure that you're running the 9.0.3x326 version of FMS.

Steven

Hi Steven,

I have not enabled encryption, nor external authentication. I'm not aware of any settings for database visibility, where are these?

We are running 9.0.3.325. I will update over the weekend, and do a restart.

I'm not aware of any settings for database visibility, where are these?

Security tab of the Admin Console.

Steven

Ah right, it's set to list all databases.

Over the weekend I updated the server to 9.0.3.326. No change, I still can't connect from the Win7 machine.

If I open a telnet connection on port 5003, 50003 or 50006, I get a blank screen with command prompt. If I try the same on any other port, I get connect failed. This suggests that the server is responding on the correct ports.

How else can I fault find this?

I hit this issue yesterday. Spent an afternoon trying to fix it.

In my case on Windows 7 I installed FMPA 10.0v1 and updated it to 10.0v3. It can see hosts but not the files.

Solution: uninstall FMPA 10 and re-install using a 10.0v3 installer. Don't install an older version and patch up.

If you need a 10.0v3 installer for FM Pro (not Advanced) download the Trial version from the FMI web site and put your real company name licence key into it.

I spoke to support and they identified the issue was down to a corrupted server.pim file (in the Program Files/Setup directory I think). They told me copying this file from another machine would solve the issue, but as I don't have another Win7 client I had to reinstall.