[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 331
  • Last Modified:

Sysvol not replicating to other DC's server 2003

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
Bitcoin
Asked:
Bitcoin
1 Solution
 
MaheshArchitectCommented:
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
 
BitcoinAuthor Commented:
No there are other dc's that use this as a replica source and they are now affected. ill try the port tool
0
 
ZenVenkyArchitectCommented:
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
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
DrDave242Commented:
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
 
BitcoinAuthor Commented:
Afer all that it looks like a flaky network link to our head office.
0
 
BitcoinAuthor Commented:
i solved it
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now