Archived from groups: microsoft.public.win2000.active_directory (
More info?)
Paul,
Thanks for the reply.
When I run replmon on both DCs, I see a reference to a "**Deleted Server #3"
under current trasitive replication partner status for
Directory Partition: DC=neopharm,DC=com,
Directory Partition: CN=Configuration,DC=neopharm,DC=com and
Directory Partition: CN=Schema,CN=Configuration,DC=neopharm,DC=com"
Bill
Paul Bergson" wrote:
> Try this
> Start up replmon (Replication Monitor) and add all you servers. Right
> click on one of your servers and select "Generate Status Report", give it a
> name and then select ALL tests. Once complete go through this log and look
> for errors.
>
> --
>
> Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Bill Mark" <BillMark@discussions.microsoft.com> wrote in message
> news:FA271E9D-A874-4629-8957-55F77A8A0B44@microsoft.com...
> > Did what you recommended. The logs did not show any failures.
> >
> > Bill
> >
> > "Paul Bergson" wrote:
> >
> > > Stuff the following in a batch file and run, make sure you change
> > > server_name to a dc in your environment.
> > > If you haven't loaded the support tools they should reside on your
> install
> > > cd at d:\support\tools\setup.exe
> > >
> > > @echo off
> > >
> > > c:
> > > cd \
> > > cd "program files\support tools"
> > >
> > > del c:\dcdiag.log
> > > dcdiag /e /c /v /s:server_name /f:c:\dcdiag.log
> > > start c:\dcdiag.log
> > >
> > > del c:\netdiag.log
> > > "C:\program files\support tools\netdiag" /v /l
> > > start netdiag.log
> > >
> > > del c:\repadmin.log
> > > "C:\program files\support tools\repadmin" /replsum /bysrc /bydest
> > > /sort:delta > c:\repadmin.log
> > > "C:\program files\support tools\repadmin" /showreps server_name >>
> > > c:\repadmin.log
> > > start c:\repadmin.log
> > >
> > >
> > > --
> > >
> > > Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > >
> > > "Bill Mark" <BillMark@discussions.microsoft.com> wrote in message
> > > news:A244023C-6224-4C1E-8D5C-4BA382298715@microsoft.com...
> > > > Thanks,
> > > >
> > > > I followed the instructions from the tech note, and the 2000 DC did
> not
> > > show
> > > > up in the list of DCs, so there was nothing to delete.
> > > >
> > > > The replication issue I am having is NTDS Replication DS RPC client
> 1232
> > > > warning that says there is a timeout between my DCs. Article 830746
> > > > attributes this to slow network performance, but the DCs are on the
> same
> > > > 100MB switch. I was going to change the timeout just to eliminate it
> as a
> > > > possibility.
> > > >
> > > > I can change the 'src root domain srv' parameter to the the main DC,
> but
> > > it
> > > > concerns me that it is there to begin with.
> > > >
> > > > Any other thoughts would be appreciated.
> > > >
> > > > Bill
> > > >
> > > > "Paul Bergson" wrote:
> > > >
> > > > > Follow the instructions in the link below.
> > > > >
> > > > >
http://support.microsoft.com/?id=216498
> > > > >
> > > > > --
> > > > >
> > > > > Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
> > > > >
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > >
> > > > > "Bill Mark" <Bill Mark@discussions.microsoft.com> wrote in message
> > > > > news:276E7C4A-448D-4DFB-9E77-53B370AB787D@microsoft.com...
> > > > > > I phased out a 2000 DC. I now have two 2003 DCs. I did adprep,
> > > completed
> > > > > > the process on mangled attributes (we upgraded Exchange 2000 to
> 2003),
> > > > > moved
> > > > > > the FSMO roles and demoted the server. Today I noticed that the
> DCs
> > > don't
> > > > > > seem to be replicating. I found KB830746 and was checking both
> DCs
> > > when I
> > > > > > noticed that in
> > > HKLM\system\currentcontrolset\serveices\ntds\paramters,
> > > > > there
> > > > > > is a registry parameter 'src root domain srv' whose value is my
> old
> > > 2000
> > > > > DC.
> > > > > >
> > > > > > I'm not sure what to do at this point. Do I just need to update
> that
> > > > > > paranter? How do I clean up from the failed demotion? Might
> there be
> > > > > other
> > > > > > issues, i.e. corrupt AD; Exchange issues?
> > > > > >
> > > > > > Any assistance is greatly appreciated.
> > > > > >
> > > > > > Bill
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>