|
Question : LDAP bind unsuccessful (Exchange 2003)
|
|
We have Exchange 2003 setup on Windows 2003 which is connected to one domain with two domain controllers, all on the same site.
Active Directory is hosted by these two servers with the five domain roles distributed between both servers. server1 holds the PDC emulator, Domain-Naming master and the Schema, server2 holds the RID master and Infrastructure master for the domain. server1 being the first controller in the domain has the Global Catalog.
We've had a problem recently where "server1" has shut down and this affects Exchange which stops working, you cannot log onto the information store. Exchange has the following in event viewer
Event Type: Error Event Source: MSExchangeAL Event Category: LDAP Operations Event ID: 8026 Date: 05/05/2004 Time: User: N/A Computer: Description: LDAP Bind was unsuccessful on directory xxxxx for distinguished name ''. Directory returned error:[0x51] Server Down. DC=xxxx,DC=xxx,DC=xxx
For more information, click http://www.microsoft.com/contentredirect.asp.
Event Type: Error Event Source: MSExchangeAL Event Category: Service Control Event ID: 8260 Date: 05/05/2004 Time: User: N/A Computer: Description: Could not open LDAP session to directory 'xxxxx' using local service credentials. Cannot access Address List configuration information. Make sure the server "server1" is running. DC=xxxxx,DC=xxx,DC=xxx
For more information, click http://www.microsoft.com/contentredirect.asp.
Any suggestions as to how I could get around this problem if "server1" goes down ? I'm new to all the AD stuff and am looking for a little guidance
Many thanks Steve
|
Answer : LDAP bind unsuccessful (Exchange 2003)
|
|
I think you will have to do that manually , anyway you will need to Promote the new server to a Global Catalog server once the server1 goes down
|
|
|
|