We have a PDC that we're trying to sync to an external time source.
1. It has been setup with: w32tm /config /manualpeerlist:"time-b.nist.gov time.nist.gov" /reliable:yes /update" (and various other versions of this command; such as, adding ",0x1" after the peerlist names. The w32tm service has been restarted after entering the command and the registry indicates this is an "NTP" server.
2. The server is behind a firewall; however, running the following command: "w32tm /stripchart /computer:time-b.nist.gov /samples:5/dataonly" consistently returns time difference statements similar to: "09:12:43 d:+00.2187338s o:+127.5151578s [ . . . ]", which I take to mean that our PDC IS able to see the external time server, to query it, and to successfully receive time information from it.
3. If the following command is run: " w32tm /resync /rediscover", it will time out with a reply that "The computer did not resync because no time date was available".
4. The Event Log shows the following event each time the w32tm service is restarted:
Event Type: Warning
Event Source: W32Time
Event ID: 12
Description:
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."
---
What to do so this PDC will actually sync to the external time source? Thanks!
|
