Solved

Sysvol not replicating to other DC's server 2003

Posted on 2014-04-23
6
310 Views
Last Modified: 2014-05-19
hi guys

hoping someone can help

got an AD replication issue. Looks like the sysvol directory isnt replicating the server in question. I found that the sysvol folder on the server was corrupted so i deleted it (took a copy backup)

Ive done the burflag reg mod, done a couple of other usual things mentioned on the web.

the funny thing with this is its saying that has become a domain controller and all lights are green, dc diag is throwing one error about Netlogon share couldnt be accessed which i think has something to do with the whole sysvol issue.

Its been 3 hrs and nothing has appeared on the server and all the servers relying to push the replication out from the server with the initial issue.

any help appreciated.

thanks
0
Comment
Question by:Bitcoin
6 Comments
 
LVL 35

Expert Comment

by:Mahesh
ID: 40018848
what about other domain controllers ?

Do they all have Sysvol and netlogon shared ?

If the issue exists with single DC, check if AD ports are opened as appropriate ?

Download Portqueryui toll from Microsoft to check port blockage if any ?

Are you getting event id 13568 on any of other DCs \ affected DC ?

If the issue exists with single DC, probably you can demote \ promote it once and check if its resolves your issue

Mahesh.
0
 

Author Comment

by:Bitcoin
ID: 40018853
No there are other dc's that use this as a replica source and they are now affected. ill try the port tool
0
 
LVL 9

Expert Comment

by:Zenvenky
ID: 40024555
First question: how many DCs are there in the domain and how the site connections are configured?

When you run Repadmin /replsum and repadmin /showreps on all DCs do you see any errors. Try this atleast on 2 DCs and let us know. If repadmin output is clean then nothing to worry. Using this link fix DNS issues on all DCs: DNS Best Practices

Once it is done, take backup of SYSVOL on all DCs and turn of FRS service. Now compare all SYSVOL data with one another and whichever has updated data perform authoritative (D4) restore and restart FRS service.

Once you get Event ID 13516, perform non-authoritative restore on one DC and turn on FRS service. Once you see Event ID 13516 on that DC as well. perform the same with other DC.

SYSVOL replication
0
 
LVL 25

Expert Comment

by:DrDave242
ID: 40052190
Ive done the burflag reg mod, done a couple of other usual things mentioned on the web.
Did you set Burflags to D2 or D4? Also, are there any errors in that server's File Replication System event log?
0
 

Accepted Solution

by:
Bitcoin earned 0 total points
ID: 40066539
Afer all that it looks like a flaky network link to our head office.
0
 

Author Closing Comment

by:Bitcoin
ID: 40074485
i solved it
0

Join & Write a Comment

The password reset disk is often mentioned as the best solution to deal with the lost Windows password problem. In Windows 2008, 7, Vista and XP, a password reset disk can be easily created. But besides Windows 7/Vista/XP, Windows Server 2008 and ot…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now