Windows Server 2003, NTP and W32Time issues

crsrvn used Ask the Experts™
I have created a new domain controller on my domain to hold all fsmo roles, and have transfered the roles to it successfully. I am receiving the follwing error in my event logs.
Event Type:      Warning
Event Source:      W32Time
Event Category:      None
Event ID:      12
Date:            5/30/2007
Time:            5:44:08 PM
User:            N/A
Computer: MDC
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.  It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source.  Otherwise, this machine will  function as the authoritative time source in the domain hierarchy.  If an external  time source is not configured or used for this computer, you may choose to disable  the NtpClient.

It seems as if I am having some issues with NTP and W32Time. I have several buildings that I administer all within 25 miles of each other. 3 of my buildings are conneced to T1 lines from my ISP, my other 3 buildings are close together and are interconnected with fiber optics and all feed from a single 100MB fiber link from my ISP. Can anyone help me resolve these time synchronization issues?

Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Is there a firewall blocking NTP (port123)?
Has the PDCe been configured to sync with an external source?

The PDCe could be configured to free run.

See ms art:

There is a tool used for testing a verifying w32time it is w32tm /? run it from a cmd prompt .


So I should configure my PDC emulator to sync with an external source, and then have my other DCs sync with the PDC emulator?

You could allow the PDCe to free run (sync off it's self) or sync to remote NTP server.  If wnt to ensure accurate time sync externally.

The other DC's should already be looking at the PDCe for there time.
Check by logging on to a DC from the cmd run w32tm /monitor.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial