Hi, on the other servers there are no sysvol shares at all.
Not touched the servers, the only thing i did was demote a DC and all this happened.
Already in a VM environment will make a copy and try on the internal network.
ok so if i make a backup and imediently restore it should fix it?
thanks for the tips
What caused them not to replicate in the first place?
No idea, i wish i did know nothing in the event log to indicate why. It happened when i demoted a DC.
I had another possible solution, demote the bad DC and rebuild the sysvol like this - Windows Technical Issues Blog: How to rebuild the SYSVOL tree when none exists in Active Directory
what will actually need rebuilding? will it be the group policies? I take it users will be fine? Has anyone done this before?
I had a similar problem when one of my DCs went down unexpectedly due to a bios chip corruption.
Both running win2ksp4
When eventually got it back up forgot to set the time in the bios (due to oversite and pressure to get back up) and this caused the NTFRS to time out and this is what i think has happened to yours as it cannot connect to the other DCs which it replicates with.
All I can say is that it is fiddley but if you search for NTFRS timeout in google for the type servers you have I am sure you will find what you are looking for.
good luck :-)
Have just seen your post and this is what i had to do :-)
Thanks bossman, it is a VM so i know it wasn't what you said. I will have a look, how easy was it to fix?
Originally Posted by bossman
I have managed to get AD replicating i just the those errors and sysvol is messed up.
Would i be going the best way about it demoting the problem DC and then rebuilding sysvol on the other?