troubleshooting Question

NTFRS - Journal Wrap Errors detected on Domain Controller at Site Name

Avatar of voipguy
voipguy asked on
Windows Server 2003Microsoft Legacy OSMicrosoft Server OS
5 Comments1 Solution965 ViewsLast Modified:
3 is company but 4's a crowd....

Okay, I have a Server 2003 R2 based network that covers users at 3 locations (star network topology) with about 10 computers at the two outlying locations and about 25 at the central location.  There is a DC at each location (total of three).  The network was humming along with no problems when about 6 weeks ago, a consultant doing some other work for this company asked if he could fire up an old server in the rack that has been turned off since before I got here.  I didn''t think anything about it and said "okay go ahead and use it".  

Right about that time the DC at the central location (which is also where this old server was restarted) began to get the following error: NTFRS - Journal Wrap Errors detected on Domain Controller at Site Name.  I thought it was really strange to all the sudden be getting these errors and I've been researching what to do about it.  

Well, fast forward to about two days ago, I made some changes to a couple of GPOs on the central DC but they are not getting out to the clients.  GPUPDATE /FORCE wasn't and still isn't working.  I double checked everything in the GPO's but still no joy.  So I checked the DCs listed in "AD Sites and Services" and low and behold, the server that was turned off since before I arrived and was then turned on about six weeks ago is listed in there with the other three DCs I would expect to be there!!!!!  When I look at each of the 4 servers, the 3 servers I expect to be there have NTDS Settings listed as objects.  The johnny-come-lately, party-pooper server (the 4th server) has no NTDS settings - none, nothing, notta, zilch, zip.  It has no attributes listed; it's just kinda sitting there acting like an uninvited guest.  

BACKGROUND:  I was recently told that the domain was migrated to a new DC (the current central DC) by a previous IT mgr about 6 months before I got here.  In hindsite, and without any network documantation to go by, it appears he replicated that central server out to the two DCs at the outlying locations.  I'm assuming the 4th server is an old DC.

QUESTION: is three-fold: 1) can this 4th DC be causing confusion (through replication errors) with the legitimate DCs which would interupt the propigation of the GPO's out to the network clients?  I'm guessing it will.  Question number 2), if so how do I best get rid of this 4th DC without turning it off? (it's now fulfilling a role on the network) and question 3), how do I make the other DCs happy again and functing properly as if the 4th was never there?

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 5 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 5 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros