Server 2000 Replication Help!!!!

[mmoseley]

Hiya!

Got a huge problem that is really bugging me!

We've got 3 DC's on our network, 2 of which can replicate to each other but the 3rd one just doesnt wanna know! So its so annoying have to change group policy settings on the one thats not replicating and then go and change it on the other server that is replicating!

Ive used repadmin (?) replmon (?) and the results say all is well??? Help im out of ideas?!

Thanks Mart

[SYNACK]

No useful entries in the event log, have you tried recreating the replication links in AD sites and services?

[bio]

try to recreate the replication links manually (no auto) in AD sites and services and see what happens.

[mmoseley]

Hiya,

Thanks for your replies, ive manually recreated the replication links and still no good!,

Although if i create a GPO on the replicating servers it will appear on the non replicating server, BUT i get the error "system cannot find the file specified"

Any ideas? the NETLOGON doesnt replicate either

Thanks for your help!

[SteveMC]

You've probably already found this page, but if not, it's worth lookup at for hints on what could be wrong.

Alternatively, if it's not got any of the FMSO roles on it (or you manage to transfer them following this procedure), you could always demote it back to a member server. Then - after making sure there were no traces left of it in DNS (aside from the A record and the reverse lookup entry) - you could promote it again.

There's details on doing so in this MS KB article.

I had to do something similar recently after a domain rename on a server 2003 network went screwy.

Oh, and one other thing, - they are all synchronizing their clocks (and your Primary DC is configured to sync with an external source, as per KB216734)?

[FN-GM]

SteveMC has pretty much said my thoughts. But i have just got a few questions

Is the domain controller with the problem on the same site as the others?
Do you have any firewall or AV installed?
What elese does the server do?

[Ric_]

When I had some replication problems, ChrisH told me about Ultrasound - see http://www.microsoft.com/downloads/d...displaylang=en - which sorted my problems out in no time!

[FN-GM]

oh another thing, check you have plenty of disk space on the problematic server.

Looks an handy tool Ric, just added that to the favourites for the feature.

[mmoseley]

Ok Chaps, found out how to sort the problem out (Please excuse me but ive got no idea why or how it did it)

I examined the event logs and saw a big log telling me that basically it couldnt replicate, and gave me a few suggestions (i also looked at the other DC's and they said it couldnt communicate)

so tried a few of the suggestions from the event log like chkdsk *It also said that C: may have recently been formatted???? lol*


So i went into regedit and went to -> HKEYLOCALMACHINE - system - currentcontrolset - services - ntfrs - paramaters and added the following DWORD

"Enable Journal Wrap Automatic Restore" and the value 1.

It straight away kicked into life deleting the sysvol and netlogon and then recreated it and bobs ya uncle'!

If anyone can shed some light on this please do

Thanks Mart

[bio]

Interresting fix.. here is some extra info:

Troubleshooting journal_wrap errors on Sysvol and DFS replica sets
Folder name is changed to "FolderName_NTFRS_<xxxxxxxx>"

regards
bio..