That's not exactly bare-bones Ideally you wouldn't have those other roles on your FMS box.
See if the info in this thread helps: Re: Installing FileMaker Server 14 on Windows Server 2012 R2 without Internet Access
1 of 1 people found this helpful
During my installation it complained about the ports 443, 50003 & 50004
443 was solved by stopping the service "World Wide Web Publishing Service" (the same will help for port 80)
50003 & 50004 was solved by stopping the service "DNS Server"
After the installation I started the services again.
Ports 50003 and 50004 are very crucial to FMS functioning so I would be careful leaving the DNS service on the FMS box. On the next reboot, when the DNS service starts before FMS does, FMS may not be able to claim those ports.
I will try to change the start of the dynamic ports according to this page:
Default Dynamic Port Range
Port Range: 49152-65535
The Dynamic Port Range has been changed in the Windows Vista, Windows 7 and Windows Server 2008. By default, a fresh Windows Server 2008 installation will have this Dynamic Port Range configured. To see the port range, you can use the following commands:
NetSh INT IPV4 Show DynamicPort TCP
NetSh INT IPV4 Show DynamicPort UDP
To set or change the Dynamic Port Range:
NetSh INT IPV4 SET DynamicPort TCP Start=1024 num=65535
NetSh INT IPV4 SET DynamicPort UDP Start=1024 num=65535
I ran into this same issue and resetting the bottom end of the range that the DNS service used worked perfectly. It's THE way to have FMS and DNS peacefully co-exist. In my case, there are only a handful of FileMaker clients hanging off the box, so there isn't any performance impact to speak of.
I had this issue too. I just set the num of opened ports to a lesser value.
Open a command shell as administrator and run these two commands...
NetSh INT IPV4 SET DynamicPort TCP Start=49152 num=800
NetSh INT IPV4 SET DynamicPort UDP Start=49152 num=800
I had to stop/start the DNS service after doing so, then install would proceed.
Server itself uses localhost for DNS, but workstations are all using public DNS.