If you’re seeing
13505 & 13506 check out the links below: http: http: http://www.experts-exchange.com/Operating_Systems/Q_21579612.html Thanks... ... ... ... Sergio J. Olivarez -
Contractor Phone # (520)
538-2909 DSN: 879-2909 GD-NS From: Clay, Justin
(ITS) [mailto:[EMAIL PROTECTED] Yes I did. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Olivarez, Sergio J Mr
ANOSC/FCBS Did you delete the DC
in AD Sites and Services? Thanks... ... ... ... Sergio J. Olivarez -
Contractor GD-NS From: Clay, Justin
(ITS) [mailto:[EMAIL PROTECTED] 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
|
- RE: [ActiveDir] NtFrs Errors Olivarez, Sergio J Mr ANOSC/FCBS
- RE: [ActiveDir] NtFrs Errors Clay, Justin \(ITS\)
- [ActiveDir] Ntfrs Errors Clay, Justin \(ITS\)
- Re: [ActiveDir] Ntfrs Errors Umer Y
- RE: [ActiveDir] Ntfrs Errors Olivarez, Sergio J Mr ANOSC/FCBS