In addition to AD Sites and Services, check under System\File Replication Service\Domain System Volume (Sysvol share)\ for any leftover frsMember objects.


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clay, Justin (ITS)
Sent: Tuesday, February 14, 2006 1:28 PM
To: [email protected]
Subject: [ActiveDir] NtFrs Errors

I’m seeing errors 13555 and 13552 in the event log ever since one of our DCs died and had to be pulled out of AD. When the DC died, I did the following:

 

1.      Seized its PDC role

2.      Removed all entries for this DC using Metadata cleanup in ntdsutil

3.      Followed the rest of the steps outlined for Windows 2003 pre-SP1 here: http://support.microsoft.com/default.aspx?kbid=216498

 

I’ve removed all entries I can find for this dead DC (SBASVISDC03 is the dead DCs name) using ADSIEdit, Metadata cleanup, and the DNS console. I ran FRSDiag this morning and found that one of the other DCs (SBASVISDC01) still shows SBASVISDC03 as an INBOUND NEIGHBOR. Now I’ve looked and looked and cannot find where this INBOUND NEIGHBOR information is being stored.

 

What am I doing wrong? There must be some place I’m overlooking.

 

Thanks,

 

Justin Clay
ITS Enterprise Services
Metropolitan Government of Nashville and Davidson County
Howard School Building

Phone: (615) 880-2573

 



ITS ENTERPRISE SERVICES EMAIL NOTICE

The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.

Reply via email to