[frdmfghtr]

I use the time.apple.com time server for automatically correcting system time. I see the following in the console log:

Nov 5 10:56:37 M41 ntpd[185]: sendto(17.254.0.27): Can't assign requested address
5 Nov 13:49:04 ntpdate[3765]: step time server 17.254.0.31 offset -10.391952 sec

The first line occurs when OS X is trying to correct the system clock automatically; if I go into the time/date system preferences and click the lock to make changes, the clock will then correct automatically, the second line shows up in the log.

I notice that the two IP addresses are different; I've gotten previous entries that show the same error, such as

Nov 2 09:04:11 M41 ntpd[185]: sendto(17.254.0.27): Can't assign requested address

and

Nov 3 09:14:32 M41 ntpd[185]: sendto(17.254.0.27): Can't assign requested address

So it seems like if I go in to the system preferences and unlock the padlock, the time corrects to a particular IP address; auto checks seem to use a different one.

Ideas on how to get auto correcting time to work?

[JKT]

Check your Firewall settings in System Preferences>Sharing>Firewall. If you have the Firewall active, is the Network Time option checked to allow its port to be accessed through the Firewall?

If you aren't using the software Firewall, check that your router is allowing access to that port.

[ghporter]

Also try other time servers, like time.nist.gov. It might be that when you're trying the server is busy, or some other weirdness. Also, can you ping 17.254.0.27? (When I ping time.apple.com I get 17.254.0.26.)

[frdmfghtr]

The firewall rules (using Flying Buttress for my firewall rules) allow ntp to go through...I can get the clock updated if I unlock the system preferences, but not automatically.

I tried changing the address from time.apple.com to 17.254.0.31, so we'll see what happens. I'll also try other servers I've used in the past, such as the time.nist.gov you mentioned or tock.usno.navy.mil, or even the campus time server (I can't remember that address).

BTW, when I ping time.apple.com, I get the .31 address. Ping times to .27 were about 56 ms.

[frdmfghtr]

This morning I saw in the console log that the same error for the .27 address showed up; but I had the .31 address specified in the system preferences. Again, unlocking the preferences resulted in a successful sync with the desired time server.

Using time.nist.gov resulted in

7 Nov 08:37:30 ntpdate[5828]: no server suitable for synchronization found
7 Nov 08:38:33 ntpdate[5833]: no server suitable for synchronization found

but tock.usno.navy.mil worked.

7 Nov 08:38:44 ntpdate[5834]: adjust time server 192.5.41.41 offset 0.004232 sec