Thank you for your post!
We created two different DSNs using two separate machines (one OS X 10.10, one OS X 10.11) using the FileMaker ODBC Driver. The connection to FileMaker Server 14 was successful in both cases. The Actual Tech drivers would only be necessary for pulling data from a third party. If using External SQL Data Sources you might see: Which ODBC data sources/drivers are supported with External SQL Data Sources?
Can you explain in more detail what the data source is (FileMaker or Third-Party) and where the data is going (FileMaker or Third-Party)?
Some more detail. FileMaker server runs V. 184.108.40.2064 and hosts a database with one table for remote access thru ODBC by third-party software. Assume MS Query as the external user. On the client machine FileMaker ODBC driver version 15.0.6 is installed and used in a system DSN connecting to the server. Connection does succeed with IP address, but not with DNS name This is for MacOS 10.11. as the client system. It works under same conditions for a second machine in the same network running MacOS 10.10.
(Will check for Port issues now anyway)
If on the server (second machine) runs FileMaker Server V. 15.0 both machines can connect with IP address and DNS name.
A third machine running MacOS 10.11. on a different network cannot connect to either of the servers with port 2399 checked and open.
(Btw. Actual distributed FileMaker ODBC driver and the linked package above from FileMaker help contain the same driver.bundle)
1 of 1 people found this helpful
First issue solved: our network was not completely transparent for messages on port 2399.
The two different server engines and MacOS masked the problem.
Will check tomorrow with client's site.
Thanks for your support and assistance!