DCDiag advertising test failing. SYSVOL and NETLOGON shares not replicating

I've 2 site. HQ and Branch. There are 2 DCs in the HQ site. The primary server is on HQ. In the branch site also have 2 DCs.

I've just promoted a server to be branch site DC2. The DNS setting of the server is primary DNS point to itself and secondary DNS point to branch DC1.

I type net share and found sysvol and netlogon not shared. Run dcdiag and will get advertising test failed.

I also found the event log of File Replication service with error 13508.

I refer to this troubleshooting http://technet.microsoft.com/en-us/library/bb727056.aspx

But still gets error from dcdiag and sysvol and netlogon not shared.
Who is Participating?
sweehanConnect With a Mentor Author Commented:
I follow this resolution by microsoft http://support.microsoft.com/kb/290762

and the netlogon and sysvol are shared and replication are ok.
Thomas GrassiSystems AdministratorCommented:
What cddiag did you run?

@echo off
dcdiag >dclogx.txt
dcdiag /test:registerindns /dnsdomain:FQDN >>dclogx.txt
dcdiag /c /v >>dclogx.txt
dcdiag /test:dns >>dclogx.txt

run this and post
Dirk MareSystems Engineer (Acting IT Manager)Commented:
In dns management under server name and under domain name

Right click and go to properties
Go to name server tab

Make sure that all DNS servers are listed and that the correct IP is listed next to the correct server if you are not using ipv6 you can remove it from the list..
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

sweehanAuthor Commented:
File attached.
Thomas GrassiSystems AdministratorCommented:
After a quick review I see many errors it is late I will review in detail later

First glance DNS is a problem

Can you check your DNS a records and pointer records make sure the IP addresses are correct for each server make sure ipv6 is disabled on all network adapters and is not registering to DNS

Also each dc must have it self as the DNS server first entry must be the same IP address
sweehanAuthor Commented:
Checked the a records and pointer records. The ip addresses are correct. IPv6 has beeen disabled
Thomas GrassiSystems AdministratorCommented:
can you ping by FQDN or only by ip address

ping JB-DC2.asis.edu.my what happens?

ping JB-DC3.asis.edu.my what happens?


You have 4 DC's correct try fro each one to ping each other by fqdn

also try from a computer on the network
sweehanAuthor Commented:

ping from all the DC by FQDN. The ping returns the IP of the DCs are accurate.

I found that

EP-DC2 and JB-DC2 has error "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR" with event id 13568

EP-DC2 and JB-DC2 also has warning with event id 13562

EP-DC3 and JB-DC3 has warning with event id 13508
sweehanAuthor Commented:
I've try this solution from this link and my new domain controller is able to work properly already.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.