Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange trying to LDAP Bind to a non-existant server

Status
Not open for further replies.

irbk

MIS
Oct 20, 2004
578
US
Last week our Schema master and Domain Naming Master, for what ever reason, lost it's computer account. It could no longer communicate with AD. I couldn't run a DCPromo to remove it from AD as a DC, so I couldn't take it cleanly off the domain. I didn't have any choice but to yank it off the network, format C:\ and start from scratch. I managed to seize the roles of Schema Master and Domain Naming Master on a different DC, used ntdsutil to do a metadata cleanup, and built a new box to be the Schema Master, Domain Naming Master, Global Catalog, and CA. I've got all that transferred over cleanly except for 1 thing. I keep getting the following error on our exchange server
Code:
   Event Type:	Error
Event Source:	MSExchangeAL
Event Category:	LDAP Operations 
Event ID:	8026
Date:		8/14/2008
Time:		4:40:58 AM
User:		N/A
Computer:	<servername>
Description:
LDAP Bind was unsuccessful on directory <oldserver> for distinguished name ''. Directory returned error:[0x51] Server Down.    

For more information, click [URL unfurl="true"]http://www.microsoft.com/contentredirect.asp.[/URL]
The oldserver that exchange is trying to do an LDAP Bind to no longer exists. How do I get exchange to start looking at a different server?

Thanks in advance.
 
Check your Site and Services to see what's available to the server.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

There are no more PDC's! There are DC's with FSMO roles!
 
Davetoo - Could you be a bit more specific? I'm not sure what you mean by "Check your Site and Services to see what's available to the server" The Exchange server isn't a DC so it wouldn't show up in AD Sites and Services.
 
I figured out the error. Found this article looks like the Recipient Update Service settings needed to be changed. I've changed the settings and expect the error will go away. Thanks for the help!
 
use ntdsutil to do metadata cleanup and get rid of references to the old GC/DC/

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top