Synchronizing RedHat to two W2k Domain Controllers (was: Newbie at NTP)

In article <cc6ead760709200345u60319678nbfbdfd0bd2513182@xxxxxxxxxxxxxx>,
dummycerberus@xxxxxxxxx (Dummy cerberus) wrote:

I have Win2K domain with two DC... I would like my RedHat Enterprise
Linux servers get synchronized to the PDC through NTP.

That is a bad idea. Even when running good ntp software, Windows is not
the best time server. You should transfer time in the other direction.

If you really want to do what you say you want to do, you will need a proper
implementation of NTP on the Windows box. That means installing Windows
2003 with a recent service pack or installing the reference implemenation of
NTP (basically the same source code as you run on Linux). If you take the
first approach, you will need to provide a real time server for the domain
controller, as Windows 2003, SPx is more honest about estimated errors (root
dispersion) than a correct implementation of the protocol. If you use the
reference version, it is possible to claim that the server knows the correct
time, but this is strongly discouraged. It is also possible to attach some
of the possible hardware reference clocks, I believe, although you need
Unix or Linux for a full range.

about any error... ntpdate seems to work ok at command line with both

ntpdate is deprecated, although it is much more tolerant of broken
time servers - basically it doesn't plausibility check the results as
well.

hosts... but if I type ntpd -d -q I get this error:

Most of these are information, not error.

addto_syslog: bind() fd 4, family 2, port 123, addr 0.0.0.0,
in_classd=0 flags=8 fails: Address already in use

This means that another instance of ntpd was already running.
You should probably have looked at the relevant system log file to see
what the first instance was saying, but I expect you will find it is
rejecting the PDC due to an excessive root dispersion, which is best seen
using the ntpq rv command for the association (use ntpq assoc to get the
association numbers).

[ Subject changed to properly summarise the question. ]
.

Relevant Pages

  • Re: ntp linux daemon drift apart from Windows Net Time Server
    ... I am trying to synchronize a linux box to an NT server ... The NT server is running SNTP and not NTP. ... The windows XP box takes time from: ...
    (comp.protocols.time.ntp)
  • Help -- Problem Syncing With time.nrc.ca
    ... time.chu.nrc.ca (as well as one other NTP time server). ... But my Linux box gets a Kiss of Death packet when trying ... # restrict default nomodify nopeer ...
    (comp.protocols.time.ntp)
  • Re: RH9 NTP trouble
    ... >>machine to the real servers (running ntpdate) and this machine becomes ... >>time server for rest of the host on the interanet. ... As already said - sync your master server to extenal NTP ...
    (comp.os.linux.misc)
  • Re: Simple ntp setup, but I must be doing something wrong
    ... When I get things working properly I will switch to using the pool ntp servers so that I am not relying on a single ntp server. ... Over the last several weeks I have been trying to get the NTP service running properly on my company linux file server, but am not having much success. ... My objective is to synchronize my linux server with a secondary time server or one of the ntp pools, then synchronize a handfull of desktop windows systems with the file server. ... Below is my config file, the output of ntpq -p and ntpq -pn, and the log messages from the last restart of ntp that matches the configuration file shown below. ...
    (comp.protocols.time.ntp)
  • Re: Primary WINS Server
    ... The SNTP value on the server is as you expected, ... of the Linux box (which is not running a time server) as the time server. ... is synching with the SBS. ...
    (microsoft.public.windows.server.sbs)