Time Sync between Server 2003 and Client XP

[Rockstar101]

Hi,
Is there a way to determine how the client is being sync'ed with the Domain Controllers? I've read there's 3 different ways to time sync.

1) By synching to a reliable time server on the Internet.
2) By synching to an locally-connected hardware time source such as an atomic clock.
3) By relying on its own internal CMOS clock for reliable time.

Where would I look and how would I be able to tell?

Thanks for your help!

 

[LWComputingMVP]

A windows domain, if configured properly, will have all the clients sync automatically with the DC that holds the PDC emulator FSMO role. If I remember correctly, you should see event log messages if this is not happening (and maybe if it is).

-Lee

Those who ask why, learn

http://www.lwcomputing.com

 

[theravager]

You can pretty much ignore clients, all you have to do is configure one server to sync somehow, generally the server with the pdc role is the best bet. Just do a search on ntp and server and you will find out all you need to know, there is multiple ways to configure ntp.

 

[LWComputingMVP]

theravager,

I suggest you read up on the Windows Time Service and Active Directory. There is no such thing as a PDC in an Active Directory domain. There is a PDC emulator, but it's not the same thing - it's a FSMO Role.

As for the time sync, the Windows Time service should sync with the PDC emulator - this should be AUTOMATIC with no need for you to do anything. This is because Active Directory relies on Kerberos for authentication which requires clients and servers to be "close" in time.

-Lee

Those who ask why, learn

http://www.lwcomputing.com

 

[pagy]

A windows domain, if configured properly, will have all the clients sync automatically with the DC that holds the PDC emulator FSMO role.

Really, why sync them all to the PDCe?? Time sync hierarchy is; clients sync their time with the DC that authenticated them, Domain controllers sync their time with the PDCe and, if configured to do so, the PDCe syncs time with an external time source.

Paul
MCSE 2003
MCSA 2003
MCITP Enterprise Administrator

If there are no stupid questions, then what kind of questions do stupid people ask? Do they get smart just in time to ask questions?
Scott Adams

 

[jbarelds]

pagy is correct,

Half a year ago I had a project focussing on time synchronisation. You need to configure your DC holding the PDC emulator role with a couple relieable external NTP sources (TIP:

http://www.pool.ntp.org/).

Thats all.

If you leave the rest of the config untouched, the other DC's will sync with the PDC and clients will sync with the DC that authenticated them.

 

[LWComputingMVP]

Sorry - I needed that little reminder - I remembered how the PDCe handled time sync, but forgot it was only the "master" for the domain - needed the reminder and the refresher - see also:

http://www.windowsnetworking.com/articles_tutorials/Configuring-Windows-Time-Service.html

-Lee

Those who ask why, learn

http://www.lwcomputing.com

 

[Davetoo]

Just FYI, I ran into some problems a month or so ago using the ntp pool source...had to switch off to a University server that used the Navy's clocks.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!

 

[Rockstar101]

Thanks for all the great info. But is there a way to find where this setting is coming from. I ck'ed the GPO's and they're not configured. However, we have clients and in the registry we can see the NTPClient is point to a server.

Where is it getting this information from?

 

[Rockstar101]

more info: under the ntpclient folder in the registry belonging to one of the clients there is the value/key "specialPollTimeRe..." and the value is pointing to a server.

I'm trying to figure out where to look to see how this value is getting populated.

I've ready ck'ed AD GPOs on PDCe where server is FSMO and their not configured. Any ideas...thanks.

 

[TechyMcSe2k]

http://support.microsoft.com/kb/307897/EN-US/

"If the computers belong to an Active Directory domain, the Windows Time service configures itself automatically by using the Windows Time service that is available on domain controllers. The Windows Time service configures a domain controller (PDCe) in its domain as a reliable time source and synchronizes itself periodically with this source. You can modify or overwrite these settings, depending on your specific needs.

 

[SteveRoadWarrior]

What happens when you do the troubleshooting steps in:

http://support.microsoft.com/kb/816042

Sometimes, I'll set the clock off by two minutes and then cycle the Windows Time service. It usually takes 35 seconds or so, but it is reassuring to see the clock get changed. Old school, I guess. Check the EV too, it is all laid out there.