Thank you for the information. I followed the article, and found that the
problematic DC that we had to remove from the network (we'll call it DCTEMP)
- was NOT available for metadata cleanup.
Where I DO see the 'ghost of DCTEMP' is when I run an MS Utility called
"ntfrsuti ds". It shows that it is a member in the File Replication Service
- is there a way to remove this entry? Or rebuild FRS, since I still get a
FRS Error 13508 (with no corresponding 13509).
Should I pose this question again somewhere, as a 'corrupt FRS' question?
1) I need to remove the DCTEMP server from FRS
2) I need to find a way for FRS to replicate the 'good' Local DNS forward
lookup zone to our Remote DNS.
Any advice would be greatly appreciated!
--
pbrill1
"Doug Sherman [MVP]" wrote:
> Try this:
>
> http://support.microsoft.com/default...b;en-us;216498
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "pbrill1" <(E-Mail Removed)> wrote in message
> news:A4E15F47-71DC-4903-8D9B-(E-Mail Removed)...
> > Recently, we had one of our 3 DC's experience numerous problems - and
> could
> > not be brought back online. We had to remove the DC from AD
> Users/Computers,
> > and choose the 3rd option (I believe) that the DC could not return to the
> > network, and AD info should be removed (or something like that).
> >
> > After the problematic DC was removed, we have had continued network
> problems!
> > - We experience FRS Error 13508, where our offsite DC does not replicate
> > with our local DC (the FRS service is operating at both servers)
> > - I have attempted to use Microsoft's FRSDiag tool, and find numerous
> > errors, some of which include references to the problematic DC that was
> > removed from the network. One of the tests that showed that the
> problematic
> > DC references were NOT removed was the NTFRSUTL DS - a DN entry still
> exists
> > (and I don't know the best way to remove it)
> >
> > The 2 part question that I have is:
> > 1) REMOVING THE REMOVED DC ENTRIES: How do I search for and remove
> > references to the problematic DC (which I thought the AD User/Computer DC
> > removal action was supposed to do). Is there a tool, or set of tools, to
> > clean up references to the removed DC in AD, etc.
> > 2) GETTING THE REMOTE DC TO REPLICATE WITH THE LOCAL (PRIMARY) DC: We are
> > also receiving NTDS Replication Errors 1863 (warning) and 2093 (error)
> > messages in the Directory Service error log that state that the remote DC
> > cannot contact a DC with a FSMO role - all of which are still located on
> our
> > local DC. I have not found any advice on dealing with NTDS Replication
> > errors 1863 and 2093 that can fix this issue (again, the server that we
> lost
> > did NOT have FSMO roles, only our local DC) - also, this - I think - is
> > related to our File Replication Service log message 13508.
> >
> > I am having to rapidly run up a steep learning curve to learn how to
> rejoin
> > the AD integrated DNS info on our W2K3 servers - any help on this
> difficult
> > issue would be GREATLY appreicated.
> > --
> > pbrill1
>
>
>
Similar Threads
Linear Mode
