Michael Badt wrote:
> Thnaks Tauno,
> I foolowed your recommendation, for several ntp servers with the following
> result:
> 26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8 10:35:44
> CEST 2005 (1)
> 26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting
>
> Any idea?
>
> Tauno Voipio wrote:
>
>
>>Michael Badt wrote:
>>
>>>Hi,
>>>I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
>>>Whenever I try, using MCC, (even with firewall shut down temporarily),
>>>several tens of seconds pass till I eventually get the message it
>>>couldn't connect with the chosen server.
>>>
>>>The respective syslog is:
>>>Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
>>>Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf
>>>%{name} ntp
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>>>/sbin/chkconfig --level 35 ntpd on
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd
>>>stop Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
>>>Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded
>>
>>This can be due to the clock being too far off the NTP time.
>>To prevent time jumps, the NTP daemon limits the error it's
>>willing to correct.
>>
>>
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>>>/usr/sbin/ntpdate pool.nrp.org
>>
>>There is no server 'pool.nrp.org'. Please check the script for
>>a misprint: 'pool.ntp.org' exists.
>>
>>Try running the ntpdate command manually, as root.

NTP is using UDP port 123 for both directions. Check that
there is nothing blocking these packets.

In the really bad case, your ISP (Actcom?) is eating them.
Ask if there is a NTP server in the ISP network.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi