Cannot set DC as Windows Time Service source

M

mtraynor.au

No matter what I try, I cannot get any servers on our domain to use their domain controllers as the source for the Windows Time Service instead of the local CMOS clock.

We have two domains hosted on the same network - I'll call them "domain" and "testdomain". Everything in "domain" is working correctly. "testdomain" has identical firewall rules and group policies as "domain", and is otherwise identical to "domain" as far as I am aware (I am relatively new to this network and these domains were created before my time). And yet no matter what I try, I cannot get any servers on our "testdomain" domain to use the testdomain DCs as the source for the Windows Time Service instead of the local CMOS clock.

This is the result of w32tm /query /peers on the testdomain PDC:

#Peers: 1

Peer: [external NTP source FQDN],0x9
State: Active
Time Remaining: 1986.2836412s
Mode: 3 (Client)
Stratum: 1 (primary reference - syncd by radio clock)
PeerPoll Interval: 6 (64s)
HostPoll Interval: 6 (64s)

Result of w32tm /query /status on the testdomain PDC:

Leap Indicator: 0(no warning)
Stratum: 2 (secondary reference - syncd by (S)NTP)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0312500s
Root Dispersion: 0.8162735s
ReferenceId: 0xCA070F0C (source IP: [removed])
Last Successful Sync Time: 5/04/2019 2:18:59 PM
Source: [external NTP source FQDN],0x9
Poll Interval: 7 (128s)

So everything there is as it should be (identical to the results of the same commands on the working domain's PDC).

Result of w32tm /query /peers on a testdomain server:

#Peers: 1

Peer: [FQDN of testdomain DC]
State: Active
Time Remaining: 43.9165223s
Mode: 3 (Client)
Stratum: 0 (unspecified)
PeerPoll Interval: 0 (unspecified)
HostPoll Interval: 6 (64s)

And yet, the result of w32tm /query /source on the same testdomain server:

Local CMOS Clock

And the result of w32tm /resync /rediscover:

Sending resync command to local computer
The computer did not resync because no time data was available.

And Event Viewer records the following Time-Service warning:

Time Provider NtpClient: No valid response has been received from domain controller TEST-DC2.testconnect.tas.gov.au after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize. The error was: The peer is unreachable.


I have run the following commands but the results remained unchanged:

w32tm /config /syncfromflags:domhier /update
net stop w32time && net start w32time

Any further help would be appreciated - I have been chasing this for 2 solid days and gotten nowhere.

Continue reading...
 

Similar threads

W
Replies
0
Views
18
wwwillster07_1970
W
I
Replies
0
Views
1K
INDYICEMAN
I
Back
Top Bottom