Premkumar Yogeswaran's Blog

Active Directory | PowerShell | DNS | DHCP | Exchange Server | VM Ware

DCDIAG – Advertising DC in Domain error

Posted by Premkumar Yogeswaran on April 4, 2012

Find the error below for the DC advertising error.

C:\>dcdiag /test:Advertising

Domain Controller Diagnosis

Performing initial setup:

Done gathering initial info.

Doing initial required tests

Testing server: APAC-SITE\DC1

Starting test: Connectivity

……………………. DC1 passed test Connectivity

Doing primary tests

Testing server: APAC-SITE\DC1

Starting test: Advertising

Warning: DC1 is not advertising as a time server.

……………………. DC1 failed test Advertising


Try each of these solutions one step at a time, re-testing after completing each step until the problem is resolved.

  1. Ensure the Windows Time service is running. On a DC it is part of the core AD functonality and should be runing even if synchronised time is not essential.

net start w32time

  1. Restart the Windows time service

net stop w32time && net start w32time

  1. Check that Network problems are not stopping NTP form functioning. Note that Windows clients do not synchronise with the DCs via NTP, this only tests the ability for DC themselves to check an external time source:

w32tm /stripchart / /samples:2 /dataonly

Error 0x800705B4 is a network timeout on the port – 123. should be replaced with the external time server you are using for a more complete test.


netdiag /fix

Netdiag is part of Windows Server 2003 Service Pack 1 Support Tools. This can also be used on Server 2008.

  1. If you received the error message: The service name is invalid earlier the Windows Time service is not even registered. Re-registering the W32time service can also fix some issues so perform these steps anyway: Re-registering the Windows Time Service
  2. Try:

w32tm /resync /redisscover

  1. Check that the DC has the PDC role:

netdom query fsmo

If it is run the following command:

w32tm /config / /syncfromflags:manual /reliable:yes /update

Microsoft’s own free NTP server can be used as shown here, but I would recommend using one in your country if not in thr US. For the UK I can recommend but there are many others.

  1. Ensure that the DC is announcing itself correctly through changing the AnnounceFlags are set correctly in the Registry. Edit the [HKLM\SYSTEM\CurrentControlSet\Services\w32time\Config\AnnounceFlags] key to a (the letter a) in hexadecimal. To allow the w32time service read the config change:

w32tm /config /update

Re-registering the Windows Time Service

w32tm /unregister
rem Ignore Access denied message if it appears and repeat
w32tm /unregister
w32tm /register
rem Before the re-register command will work you may have to reboot.

This gives a vanilla set of settings, after which the service can be restarted:

net start w32time

If you receive an error message regarding SIDs then DC will need to be rebooted again.


One Response to “DCDIAG – Advertising DC in Domain error”

  1. Leonie said

    We are a group of volunteers and openijng a new scheme in ourr community.
    Your web site offered us with valuable information to work
    on. You have done a formidble jjob aand our whole community will
    be grateful to you.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: