Tech Support Forum - View Single Post

newhouse1390 · 03-21-2007, 07:25 AM

The PDC needs to be declared an authoritative time source, which I am almost certain has already happened (all domain clients are syncing with the PDC).

So really the only thing I need to accomplish is to get the PDC syncing with an external time source.

As stated before I have followed you steps and the NTP was set, however even though the service is stopped and restarted, the clock on the PDC is not accurate (not syncing with NTP). I need to verify the accuracy of NTP <69.222.103.98>.

What is the command for initiating the sync with the given NTP?

Thanks.

03-21-2007, 07:25 AM	#4 (permalink)
newhouse1390 Member, Networking Team Join Date: Jan 2005 Location: Ohio Posts: 1,040 OS: Windows Server 2003	Re: Clock Sync issues The PDC needs to be declared an authoritative time source, which I am almost certain has already happened (all domain clients are syncing with the PDC). So really the only thing I need to accomplish is to get the PDC syncing with an external time source. As stated before I have followed you steps and the NTP was set, however even though the service is stopped and restarted, the clock on the PDC is not accurate (not syncing with NTP). I need to verify the accuracy of NTP <69.222.103.98>. What is the command for initiating the sync with the given NTP? Thanks. __________________ Because you can read this thank a teacher, because it's English thank a soldier.