Re: Issues with w32tm on AD network
- From: Martin Burnicki <martin.burnicki@xxxxxxxxxxx>
- Date: Fri, 22 Feb 2008 09:31:38 +0100
Andrew,
Andrew Hodgson wrote:
Hi,
I have had issues keeping accurate time on W32tm using an Active
Directory based network with just Windows servers. I have a Linux
workstation, and NTP on that workstation keeps loosing the time, and
going to Stratum 16. Similarly, there are Cisco routers on the
network, which also do likewise.
I am using the NTP pool, but have done this for years on a Linux
system with no problems.
Should I think about switching to NTPD on Windows, and if I do this,
will it cause an issue with both this and W32tm running at the same
time?
Though it's normally preferable to run ntpd rather than w32time, there is a
limitation if you run ntpd on a domain controller:
The domain members (workstations) will stop detecting the domain controller
automatically as their primary time source, so you'll have to configure the
domain controller explicitely as times source on every client.
If you also run any Linux or other *ix server then a better approach would
be to let the *ix machine synchromize to the pool servers, and configure
the *ix machine as "internet time source" for w32time on the domain
controller.
You should not let real NTP clients use w32time as time source, though.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
.
- Follow-Ups:
- Re: Issues with w32tm on AD network
- From: Danny Mayer
- Re: Issues with w32tm on AD network
- From: Andrew Hodgson
- Re: Issues with w32tm on AD network
- From: Ryan Malayter
- Re: Issues with w32tm on AD network
- References:
- Issues with w32tm on AD network
- From: Andrew Hodgson
- Issues with w32tm on AD network
- Prev by Date: Re: Leap second functional question
- Next by Date: Re: Leap second functional question
- Previous by thread: Re: Issues with w32tm on AD network
- Next by thread: Re: Issues with w32tm on AD network
- Index(es):
Relevant Pages
|
