Server Time Issues

[Tim Jones]

Try using a different server for one main system and then sync all of your other systems to that one master.

I’ve loaded up OS X server on one system and then use pool.ntp.org for the server and sync all of the other systems to that OS X Server system.

This has resolved a LOT of time-related issues around here for all of our systems, not just Macs.

Tim
—
Tim Jones
CTO – TOLIS Group, Inc.
https://www.productionbackup.com
BRU … because it’s the RESTORE that matters!

[Robb Harriss]

Yes, I’ve had the same issue for years. I finally gave up and set the preferences so I enter the time manually on each machine. As long as it’s reasonably close I seem to have no problem. And I have to reset the time on a machine only occasionally.

Non-linear: all the time and nothing but.

[Robb Harriss]

I’ll try that, too. I’m running Lion (latest my older Mac Pros will handle). But like I’ve said I’ve the problem for years.

Non-linear: all the time and nothing but.

[Tim Jones]

I’ve also locked our Mac servers to 10.7.5 (Mac Pro 1,1 and Xserve). If it ain’t broke, don’t fix it.

Tim
—
Tim Jones
CTO – TOLIS Group, Inc.
https://www.productionbackup.com
BRU … because it’s the RESTORE that matters!

[Scott Goddard]

The best solution I have for now is to set your server time up manually, then select ‘set date and time automatically’ and enter 127.127.1.0 in the text field. This basically makes the clock run from the local machines built in current time.

For the rest of your attached client machines, be they OSX, you can now enter the local server IP address in place of 127.127.1.0. This will sync them to the local server. For machines outside the local network you can forward port 123 to that server machine. So most likely xxx.xxx.xx.xxx:123 where x is your static public IP.

Hope that helps anyone in the same situation.

Scott Goddard

Neo Verite Limited
https://neoverite.com