Re: LDAP Bind was unsuccessful

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: David Everett [MSFT] (deverett_at_online.microsoft.com)
Date: 03/18/04


Date: Thu, 18 Mar 2004 17:22:25 -0600

These values are used to identify replication partners during dcpromo and
never used again. The dcpromo process in Windows Server 2003 just does not
clean these up.

The "Src Root Domain Srv" value is the server used when the server was
promoted as a Domain Controller and the "Src Srv objectGUID" is the
Replicator ID of that DC. If that DC still existed in your environment the
value in would be seen in repadmin /showreps (transposed).

The solution provided by Patrick look like the way to go for the Exchange
problem.

-- 
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"Patrick" <padkinson@hotmail.com> wrote in message
news:1008201c40d37$ea56b590$a101280a@phx.gbl...
> I hope this helps.
>
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;272552&sd=ee
>
> >-----Original Message-----
> >We have recently upgraded from AD & Exchange 2000 to
> 2k3.
> >I used a swing box for the rebuild of the DC's (we have 2
> >at this site).  I first built my swing and moved the
> roles
> >hosted by the PDC to it.  I also installed TS licensing,
> >Cert services, etc.  I then demoted and rebuilt my first
> >DC and moved everything back.  No issues so far.  I did
> >the same with my second DC which is also a GC.  After I
> >did that, I left the GC role on the swing while we played
> >with E3K and RPC over HTTP.  After we were comfortable
> >with it, I demoted the swing box and, after replication,
> >removed it from the domain.  Everything is working pretty
> >well, including RPT over HTTP using the second server
> (the
> >GC).  Here's where my issue is.
> >
> >Once a day on my Exchange server, I get a App log error
> >from MSExchangeAL (8026) saying that an LDAP Bind was
> >unsuccessful on directory swingserver.domain.local for
> >distringuished name ' '.  Directory returned error:
> [0x51]
> >Server Down.
> >
> >So I started looking.  I can't find any references to
> that
> >server anywhere save one.  Both of my DC's have a
> registry
> >entry under HKLM NTDS\Parameters that references the
> >server.  There are actually 2, I think.  The first is the
> >Src Root Domain Srv and lists the swing box.  The second
> >is the Src Srv objectGUID and is a hex that, I assume,
> >reflects the old server as well.
> >
> >Any idea what that entry is and how to (gracefully)
> change
> >it?  Is there anyplace else I should be looking?
> >
> >Thanks.Adam
> >
> >.
> >


Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I just promoted the remote DC last week, so I still have time to solve the replication issues. ... Domain Controller Diagnosis ... Connecting to directory service on server alpha. ... Performing upstream analysis. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to decommission a Windows 2008 DC via dcpromo
    ... Can you open and compare sysvol and netlogon share on both DCs? ... Verifying that the local machine server2, ... The File Replication Service Event log test ... Latency information for 8 entries in the vector were ...
    (microsoft.public.windows.server.active_directory)
  • Re: adding 64-bit R2 DC to existing domain
    ... Server 2003 standard edition 32-bit domain controllers. ... The schema master did not complete a replication cycle ..." ... server1 failed test KnowsOfRoleHolders ... ForestDnsZones failed test CrossRefValidation ...
    (microsoft.public.windows.server.setup)