DC in Journal Wrap - is it still taking logon requests?

[gshaw]

Until recently we had far too many DCs on the network (5!) now demoted down to a PDC, BDC and the old mailserver (to be replaced in summer) plus one more that we can't demote due to faulty RAM (BSODs on DCPROMO so need to swap memory out from a spare server until I can order some more in).

Problem is that extra DC keeps going into Journal Wrap error state, I'd guess due to the RAM problem - already fixed it once but just keeps happening, along with loadsa FRS errors.

What I'm wondering is whether it's still servicing logon requests as I've got some new scripts in NETLOGON that obv isn't being replicated and don't want random machines not working, anyone know if it's still basically online just well off the pace or whether the OS stops it responding to AD requests?

Cheers

[GlennT]

This is a replication problem by the sounds of things.
I guess it is still trying to replicate with the other DC's but failing.
Have a look at this....
http://support.microsoft.com/kb/292438
http://support.microsoft.com/kb/221111/

[gshaw]

Had to do some registry keys to get it going last time (see here)

http://support.microsoft.com/kb/290762/

but it keeps going wrong again so need to get that DC out the way for now, just wondering if it's still "open for business" using old data?

[GlennT]

You could use Replmon to check if the servers are replicating?