Posts Tagged ‘NTP’

NTP and Mavericks

Tuesday, October 22nd, 2013

Configuring NTP on the latest version of OSX is, in typical Apple fashion, almost deceptively easy.  As in previous versions of OSX any Mac can serve as an Network Time Protocol server with the check of one button.  Once this is done you’ll be able to act as a network clock for any computer on your local area network.

 

To get ntpd going, simply do the following.

 

First open your system preferences and head over to date & time

Screen Shot 2013-10-22 at 4.54.17 PMYou’ll notice that the box to update from a network time server is unhecked.  And if you look at the following port scan you’ll see that the NTP port, port 123, is closed.

Picture 1

Now check the box

Screen Shot 2013-10-22 at 4.54.21 PM

And notice that the NTP daemon starts up and listens on the correct port.

Picture 2

What could be easier?  Now get out there and synchronize your stop watches!

 

Restart time syncing in Mac OS X with Remote Desktop

Tuesday, October 30th, 2012

As batteries die in older Macs their ability to keep the computer’s clock ticking dies with them. Slight interruptions in power can reset the date to January 1, 1970, or January 1, 2000, for newer machines.

Syncing the computer’s clock to a network NTP time server can quickly return it to current time without any effort. However, Macs may not begin syncing right away. That’s a problem for users in Active Directory environments where a discrepancy in time of more than five minutes won’t allow them to log in.

Using Apple Remote Desktop (or an SSH connection to the computer), a remote administrator can issue two simple commands to restart time syncing.

First, verify the time of the remote computer using ARD’s Send UNIX command to get the current time and date. Simply enter the date command and run it as root.

Date command in ARD

This will return something like: Thr Jan 1 10:56:37 CDT 1970. Active Directory won’t allow any logins.

To correct the time use the systemsetup command to turn time syncing off and then turn it on again:

systemsetup -setusingnetworktime off
systemsetup -setusingnetworktime on

setusingnetworktime

Run the date command again and the clock should now show the current time: Tue Oct 30 11:09:26 CDT 2012. Active Directory users should be able to log in immediately.

To store this quick command for later select Save as Template… from the Template drop down menu and assign it a name.

Troubleshooting File Replication Pro

Saturday, May 2nd, 2009

Check the Web GUI.

To Check the logs via the Web Gui
- On the server, open Safari and go to http://localhost:9100 and authenticate
- Go To Scheduled Jobs and view the Logs for the 2 Way Replication Job

You can also tail the logs on the server. They are in /Applications/FileReplicationPro/logs and among the various logs in that location, the most useful log would be the syncronization log.

Many times the logs show that the server TimeSync is to fare between, the date and time are not correct. Each Server has a script you can run to resync the time. To Run this Script
Open Terminal on both First and Second servers and run
sudo /scripts/updatetime.sh

You should see output in the terminal window and in the Console related to the time&date are now in sync with the time server.

To Stop and Restart the Replication Service

Open Terminal and run the following commands as sudo
systemstarter stop FRPRep
systemstarter stop FRPHelp
systemstarter stop FRPMgmt
once the services are stopped, start them up again in the following order
systemstarter start FRPRep
systemstarter start FRPHelp
systemstarter start FRPMgmt

You also should restart the second (or tertiary) Client:
Open Terminal and run the following commands as sudo
systemstarter stop FRPRep
wait for the service to stop and then start it again with this command
systemstarter start FRPRep