General discussion

Locked

LDAP BIND Problem with Exchange 2003

By yp ·
Event id 8026
LDAP Bind was unsuccessful on directory <directory> for distinguished name ''. Directory returned error: [<error code&gt <error details>.

I have DC and Exchange server ( diffrent machines)
Winwods 2003 Standard Server and Exchange 2003
i get the above error msg at least 5/6 times a day an sometimes the exchange services need restarting
anyone has solution to this please let me know
and how to implement it

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by p.j.hutchison In reply to LDAP BIND Problem with Ex ...

Make sure you have a Global Catalog server enabled (see AD Sites and Services, there is a tick box for NTDS Settings for each DC).

On Exchange server, ensure TCP/IP settings have correct DNS IP addresses used and is using a Static IP address.

Collapse -

by yp In reply to

Poster rated this answer.

Collapse -

by p.j.hutchison In reply to LDAP BIND Problem with Ex ...

Do you have any old Exchange 5.5 servers with ADC? The Exchange 5.5 LDAP Port can conflict with AD LDAP. Changing LDAP ports can fix this.

Also, make sure Firewall is not enabled between DC and Exchange which may block essential ports.

http://support.microsoft.com/default.aspx?scid=kb;en-us;288828

Collapse -

by yp In reply to

Poster rated this answer.

Collapse -

by curlergirl In reply to LDAP BIND Problem with Ex ...

Be sure that the DC that the Recipient Update Service points to has the FSMO roles of both Global Catalog server and infrastructure master. To check the RUS properties, in the Exchange System Manager console, go to Recipients/Recipient Update Services and right click on the RUS(es) that you are using, then go to properties and look at the DC that is specified on the General tab. To check the infrastructure master role, open the AD Users and Computers console, right click on the domain name and click "Operations Masters." Click the Infrastructure tab to see which server has that role. Then, to be sure that this server is also a global catalog server, open the AD Sites and Services console and expand it to the [server name]/NTDS settings level. Right click on NTDS settings for the server and click Properties. Make sure the "Global catalog" checkbox is check; is not, check it to make the server a GC server. Then be sure this DC is the one specified in the RUS object.

Hope this helps!

Collapse -

by yp In reply to

Poster rated this answer.

Collapse -

You are...

by otaku_lord In reply to

a life saver!! The previous admin put in non-GC servers and I was having a hard time figuring out what exactly he did. Your directions pointed me right to the problem!!

Collapse -

by BFilmFan In reply to LDAP BIND Problem with Ex ...

Check that the GC isn't overlaoded and dropping LDAP requests.

There are a couple of different directory monitoring products that you can use to check this.

Collapse -

by yp In reply to

Poster rated this answer.

Collapse -

by BFilmFan In reply to LDAP BIND Problem with Ex ...

In an email to me, you asked about AD montioring products. There are tons, but my first thoughts are these:

http://www.activexperts.com/activmonitor/

http://www.aelita.com

http://www.netpro.com

In addition, Netpro offers an excellent free Ebook for troubleshooting AD issues.

Back to Windows Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums