There are errors after the SYSVOL has been shared

  • Thread starter Thread starter Jon Paskett
  • Start date Start date
J

Jon Paskett

I have 5 DC's in my forest (single site, different subnets). 4 out 5 of
controllers give me this error (There are errors after the SYSVOL has been
shared) when I run dcdiag. Each DC implicates itself as the culprit.

I am contemplating stopping all FRS, reghacking to set the one NOT having
problems to a D4 and the rest to a D2 IAW (In Accordance With) Technet
Article 315457.

Please, if you have a different solution, convince me this is not necessary
and show me a way around this problem.

TIA

<JP>
 
More info concerning the four that report this error....

I make a change to a file in the NETLOGON share of any of these four, the
changes are replicated.

I make a change on the ONE and those changes are NOT replicated. I believe
the ONE to have problems. However, with a 9 gig ntds.dit dcpromo over a T-1
is not something I look forward to.

How can I delete the entire SYSVOL (policies, scripts and all) and recreate
from scratch with out affecting the others that seem to be replicating
correctly?

Jon
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top