stevendunne
asked on
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
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
ASKER
Ok, thanks.
I've got two receipent update services in there at the moment, one is named enterprise configuration. Both of these point to "server1" which is the main domain controller.
Can I add in another receipent update service to point to the other domain controller "server" ? Or will this confuse things...
Thanks
I've got two receipent update services in there at the moment, one is named enterprise configuration. Both of these point to "server1" which is the main domain controller.
Can I add in another receipent update service to point to the other domain controller "server" ? Or will this confuse things...
Thanks
yes you can add a new RUS to point to the other DC .
check this on how to do it
http://support.microsoft.com/default.aspx?scid=kb;EN-US;319065
check this on how to do it
http://support.microsoft.com/default.aspx?scid=kb;EN-US;319065
however you cannot use it if they both represent the same domain . Yoiu can only add one server per domain .
ASKER
Ok, so I can't add another RUS in and point it to the other DC on the same domain ?
Is there anyway to get around the problem then when the main DC goes down that Exchange 2003 stop working. All the services etc are still running you just cannot get into the information store. The event above are logged. I understand that Exchange has got its tenticles locked into AD on the main DC, although so I'm told this has much to do with the schema being on DC1......
Just wondering if there's anyway to get Exchange to look at the DC2 if DC1 goes down ?
Is there anyway to get around the problem then when the main DC goes down that Exchange 2003 stop working. All the services etc are still running you just cannot get into the information store. The event above are logged. I understand that Exchange has got its tenticles locked into AD on the main DC, although so I'm told this has much to do with the schema being on DC1......
Just wondering if there's anyway to get Exchange to look at the DC2 if DC1 goes down ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, thanks. This can be closed now.
stevendunne
you need to close this post by accepting any of the answers .
you need to close this post by accepting any of the answers .
I am running a network with 2 dcs -- windows 2003 (GC) -- connected to an exchange 2003.
The problems arise occasionally (twice / day) and the errors recorded in the event viewer are shows below:
in the application section of the event viewer:
-- eventid: 8026, source: MSExchangeAL
"""""""LDAP Bind was unsuccessful on directory aias.beta.gr for distinguished name ''. Directory returned error:[0x51] Server Down. DC=beta,DC=gr """""""
-- event: 9154 source: MSExchangeSA
""""""""DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later. """""""
-- event: 2102 source: MSExchangeDSAccess
""""""""""Process IISIPM352895CF-7A25-47A2-B
zeus.beta.gr
aias.beta.gr
"""""""""
Can you give me any hints on these?
Thanks in advance.
********* I check the the two DNS SERVER and they point to there local address also exchange has primary dns .. the primaty dns , second DNS the second third DNS the internet DNS from Internet provider *********
The problems arise occasionally (twice / day) and the errors recorded in the event viewer are shows below:
in the application section of the event viewer:
-- eventid: 8026, source: MSExchangeAL
"""""""LDAP Bind was unsuccessful on directory aias.beta.gr for distinguished name ''. Directory returned error:[0x51] Server Down. DC=beta,DC=gr """""""
-- event: 9154 source: MSExchangeSA
""""""""DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later. """""""
-- event: 2102 source: MSExchangeDSAccess
""""""""""Process IISIPM352895CF-7A25-47A2-B
zeus.beta.gr
aias.beta.gr
"""""""""
Can you give me any hints on these?
Thanks in advance.
********* I check the the two DNS SERVER and they point to there local address also exchange has primary dns .. the primaty dns , second DNS the second third DNS the internet DNS from Internet provider *********
http://support.microsoft.com/default.aspx?scid=kb;en-us;272552