Server 2008 R2 failing DCDIAG - not advertising as a time server

2

When I first started working on this issue the only test that was failing was it not advertising as a time server now the following is coming up:

 Warning: LEX-DC01 is not advertising as a time server.
 ......................... LEX-DC01 failed test Advertising
 Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
    Replicating Directory Changes In Filtered Set
 access rights for the naming context:
 DC=ForestDnsZones,DC=ja,DC=com
 Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
    Replicating Directory Changes In Filtered Set
 access rights for the naming context:
 DC=DomainDnsZones,DC=ja,DC=com

I have tried:

Check the announceflags registry setting from

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config
annd verify that it is set to 10 in decimal (0x0000000A), then use w32tm /config /update

I have also tried:

w32tm /config /syncfromflags:domhier /update

then:

net stop w32time 
net start w32time
windows-server-2008-r2
domain-controller
active-directory
asked on Server Fault Sep 22, 2011 by evolvd • edited Sep 23, 2011 by evolvd

3 Answers

1

Check the announceflags registry setting from

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config

annd verify that it is set to 10 in decimal (0x0000000A), then use w32tm /config /update

See Windows Time Service Tools and Settings

Also try running

w32tm /config /syncfromflags:domhier /update

then:

net stop w32time 
net start w32time
answered on Server Fault Sep 22, 2011 by Jim B • edited Sep 23, 2011 by Jim B
0

I ended up demoting and promoting the DC in hopes of fixing the issue but it came right back. At this point time wise it might just be easier to rebuild the server. If I end up finding the fix I'll post it here.

answered on Server Fault Oct 10, 2011 by evolvd
0

I have also encountered the same issue at one of my Domain controller.I fixed this issue by registering the w32tm for that domain controller.

Steps which I followed to resolve the issuse:

  1. w32tm /unregister then Reboot your DC.
  2. w32tm /register again Reboot your DC.
  3. w32tm /config /update
answered on Server Fault Oct 10, 2015 by Vimal Kumar Tripathi • edited Oct 10, 2015 by bentek

User contributions licensed under CC BY-SA 3.0