os x server app fails on configuring services

I could have done this but it would have involved buying a GPS clock and all the hassle of trying to get that working with a Mac. The ntpd server by having this as a valid time source is then happy to itself serve to client computers. In a similar situation some larger organisations solve this by connecting a GPS clock to the server and configuring that as the the NTP source for their server. The above article does not cope with this situation. This is as far as I got before I posted this original query.

With no Internet connection the Mac server itself had no source to which it could sync, without a source to sync to it would not allow any clients to sync to it. The problem arose when I tried to do this on our other ultra-secure network which does not have an Internet connection at all. An example guide on how to setup a Mac as an internal NTP server is here I had been able to setup a Mac server as an NTP server internally on our main network and it in turn was syncing to Apple's NTP server. As a reminder directory services like Open Directory and Active Directory or more specifically Kerberos require that all the clocks of the computers on the network be within five minutes accuracy of each other.Ī lot of people will either just leave their client Macs pointing directly to Apple's free NTP servers, or may have gotten as far as setting up a Mac as an NTP server and then pointing their clients to it.

anything bigger than a home network to nominate an internal server as your internal NTP server and then have that NTP server sync itself to two or more external higher stratum NTP servers. It is common practice on larger networks i.e. OS X - both client and server include the standard ntpd software which can act as an NTP time server.

Os x server app fails on configuring services