To use Active Directory like in FMS 15 and earlier, I just want to confirm:
In the Admin Console: you still select "External Server"
Do you also have to do anything with the Microsoft Azure- is that something different from Active Directory?
Azure is microsoft's cloud. You only have to use it if you have your directory service setup that way. Otherwise it's the same setup as in 15 under the directory services tab.
Having trouble getting FMS 16 to work with Active Directory.
Users won't authenticate.
If I uninstall FMS 16 and install FMS 15 on the same 2012 R2 server, it works perfectly. If I go back to FMS 16, it stops working again.
Has anyone experienced difficulties with FMS 16 and AD?
16v1 or v2? Not aware of any problems with either but it's worth checking out.
Do you see the user's login request in the Windows security log? In any log on the AD?
What version of FM are your workstation?
Thanks for the reply.
Was on v1. Just updated to v2 and no dice.
For what it's worth, I can authenticate to a local user account I set up on the FM server, but I can't get the authentication passed on to the AD server.
That almost sounds like the OS of the FMS is not properly bound to the domain. But that would have made the same thing fail with FMS15.
As a test: can you log into the FMS16 OS with an AD account that is not admin?
No discrepancy in the clocks between the FMS machine and the AD machine?
Clocks are good.
Logged in to FM server with a non-admin account. Was able to login, but still couldn't authenticate to AD when opening the database on the server.
Welp, I went ahead and wiped the server and reinstalled everything. Now it's working beautifully.
Only thing different is I disabled IPv6 on the FM server and the DC, because I was having a little trouble getting the FM server joined to the domain. Could have been the problem all along.
Thanks for your help.
Guess I am too late with my additional thought: when you uninstalled FMS15, did you rename or delete the "filemaker server" folder that is left in 'Program Files'? If not then that could have been the culprit. Removing or renaming that folder, together with a reboot right after that and a reboot after installing FMS16 fixes many issues.
I started with FMS 16, then tried 15 when I couldn't get 16 to work. I was a bit thrown off by the extra authentication options for Cloud services like Google and Azure, so I was concerned they'd gone Cloud-crazy and disabled authentication to a local Active Directory.
Retrieving data ...