Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Exchange 2003 LDAB Bind Error Event 8026

Posted on 2011-02-22
8
468 Views
Last Modified: 2012-05-11
We have an Exchange 2003 environment and I've noticed an error:

LDAP Bind was unsuccessful on directory SERVER1.domain.loc for distinguished name ''. Directory returned error:[0x51] Server Down.    

I'm not surprised by these errors, this server (DC server) failed about a year ago and I "thought" we cleaned up all the references of it. I've searched through DNS and our AD structure but can't find the reference... Where is this reference and how can I get rid of it?

I'm preparing for a migration to 2010 and I want to ensure all the server is running optimally...

Thanks in advance!
0
Comment
Question by:pitchford
  • 2
  • 2
  • 2
  • +1
8 Comments
 
LVL 27

Accepted Solution

by:
KenMcF earned 334 total points
ID: 34957553
Did you do a metadatacleanup of the failed DC?

http://support.microsoft.com/kb/216498
0
 
LVL 3

Author Comment

by:pitchford
ID: 34957579
Yep, followed the steps and my failed server isn't listed there...
0
 
LVL 27

Assisted Solution

by:KenMcF
KenMcF earned 334 total points
ID: 34957625
Is this error just on the exchange sever? Can you run a DCDIAG and repadmin /showrepl to make sure they are both error free.

If it is just exchange I would check the DSAccess setting on the exchange server.

http://www.msexchange.org/tutorials/Closer-Look-Directory-Service-Access-DSAccess-Part1.html
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 31

Assisted Solution

by:MegaNuk3
MegaNuk3 earned 166 total points
ID: 34958639
As KenMcF has pointed out, check your Exchange DSAccess settings to see if the old DC has been manually entered there.
0
 
LVL 3

Author Comment

by:pitchford
ID: 35111214
Just trying to close this question!!
0
 
LVL 31

Expert Comment

by:MegaNuk3
ID: 35111268
Was my answer correct? Was the old Dc manually entered in the DsAccess settings?
0
 
LVL 1

Expert Comment

by:Vee_Mod
ID: 35163425
Starting the auto-close procedure on behalf of the question asker.

Vee_Mod
Community Support Moderator
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
This video discusses moving either the default database or any database to a new volume.

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question