Synching to External Time Source

[Brian D. McGrew]

Good morning,

I need to make my Windows 2000 Advanced Servers synchronize to an external
time source. I run many other operating systems including Linux, Unix, BSD
and MacOS and we all need to synchronize to the same clocks, so my questions
are:

1) How do I make my Windows AD Servers synchronize to a time source of my
specification?

2) I've been told that all Windows Clients (XP/2000Pro) use the time from
the server, is this correct or do I need to modify all my clients to
synchronize to this time source?

Thanks,

-brian
moc tod orpnoisiv ta naird
(to prevent spam, email address is typed in reverse order)

 

[Frankster]

1) How do I make my Windows AD Servers synchronize to a time source of my

specification?

Go to a command line and type:

net time /setsntp:time.nist.gov <enter>

This will hold through reboots.

This should be done on only the "PDC Emulator" Domain Controller (usually
the FSMO too). The other Domain Controllers (if any) should not be set to
sync to an external time source. They will go to the PDC Emulator by default
as long as you do not set a specific time source for them. (see below for
removing any previously set source)

2) I've been told that all Windows Clients (XP/2000Pro) use the time from
the server, is this correct

By default, yes. As long as the clients have not had thier own time sync
option specified.

or do I need to modify all my clients to synchronize to this time source?

Remove any previously specified time sync option from the clients using the
following command on the client:

net time /setsntp: <enter>

After doing this, you can check your time sync option on any machine by
typing the following:

net time /querysntp <enter>

If set, you should see the time sync option (i.e. time.nist.gov).

If not set you should see the following message:

------------
U:\>net time /querysntp
This computer is not currently configured to use a specific SNTP server.

The command completed successfully.
-------------

The above message is normal and will cause the client to sync to the
appropriate domain controller automatically.

-Frank

 

[Tym Huckin]

Use DS Clock to atomic clock syncyour server - like I do. All worksatinos
then use the net time command to sync with the server when they log on.

Tym

 

[Mohammad-Ali]

Hi Frankster

As you said:

This should be done on only the "PDC Emulator" Domain Controller (usually
the FSMO too). The other Domain Controllers (if any) should not be set to
sync to an external time source. They will go to the PDC Emulator by default
as long as you do not set a specific time source for them. (see below for
removing any previously set source)

I didn't get you why we shouldn't set the timesynch on the PDC, I have a
Win2k Domain Controller, what would happen if I set the time synch on it?

Kind Regards,
Mohammad-Ali

 

[David D]

In your mixed environment I should use NTP (http://www.ntp.org/index.html) , the "official" one.
It's likely it's already installed in you Linux,Unix and BSD computers (maybe even MacOS X as it's BSD-based.
For windows you just follow the links 2-3 steps on the NTP-page, or go directly to http://www.meinberg.de/english/sw/ntp.htm where you can find a Windows installer for NTP.
Configure it right and you have a very stable time sync.

And don't forget to disable the Windows Time Service as it interfere with NTP.

/David

 

[Richard G. Harper]

I think you misunderstood what Frank recommended.

If you have more than one domain controller you should find the domain
controller that is fulfilling the PDC Emulator role and set it up to
synchronize time with an outside source and leave the rest set up to get
their time from the PDC Emulator.

If you have only one domain controller then obviously it is the PDC Emulator
and it should be synchronizing time with an outside source

Kindly ignore the advice to do things like "run an NTP server and turn the
Windows time service off" as this is not good advice - it's actually
fighting against things that Windows and your DCs will automatically do if
you let them.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[Mohammad-Ali]

Thanks Richard, That helped

Kind Regards,

I think you misunderstood what Frank recommended.

If you have more than one domain controller you should find the domain
controller that is fulfilling the PDC Emulator role and set it up to
synchronize time with an outside source and leave the rest set up to get
their time from the PDC Emulator.

If you have only one domain controller then obviously it is the PDC Emulator
and it should be synchronizing time with an outside source

Kindly ignore the advice to do things like "run an NTP server and turn the
Windows time service off" as this is not good advice - it's actually
fighting against things that Windows and your DCs will automatically do if
you let them.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Hi Frankster

As you said:


I didn't get you why we shouldn't set the timesynch on the PDC, I have a
Win2k Domain Controller, what would happen if I set the time synch on

it?

 

[Richard G. Harper]

You're welcome.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Thanks Richard, That helped

Kind Regards,

I think you misunderstood what Frank recommended.

If you have more than one domain controller you should find the domain
controller that is fulfilling the PDC Emulator role and set it up to
synchronize time with an outside source and leave the rest set up to get
their time from the PDC Emulator.

If you have only one domain controller then obviously it is the PDC Emulator
and it should be synchronizing time with an outside source

Kindly ignore the advice to do things like "run an NTP server and turn
the
Windows time service off" as this is not good advice - it's actually
fighting against things that Windows and your DCs will automatically do
if
you let them.

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

Hi Frankster

As you said:

This should be done on only the "PDC Emulator" Domain Controller (usually
the FSMO too). The other Domain Controllers (if any) should not be set to
sync to an external time source. They will go to the PDC Emulator by
default
as long as you do not set a specific time source for them. (see below for
removing any previously set source)

I didn't get you why we shouldn't set the timesynch on the PDC, I have
a
Win2k Domain Controller, what would happen if I set the time synch on

it?