Re: LDAP Bind

Tech-Archive recommends: Fix windows errors by optimizing your registry

On Mon, 04 Feb 2008 12:08:32 +0000, Filipe Matias
<filipe.matias@xxxxxxxxx> wrote:

Hi all

I got this error today:

LDAP Bind was unsuccessful on directory <directory> for distinguished
name ''. Directory returned error: error code 0x51 Server is not available

We notice this because all our mapi clients got an error saying that
Outlook was contacting the server and it just freezed.

Owa was running fine.

The strange part is that there are no network errors and no replication
errors.


Is that your only Dc/GC?

.

Relevant Pages

  • Re: LDAP Bind
    ... LDAP Bind was unsuccessful on directory for distinguished name ''. ... Directory returned error: error code 0x51 Server is not available ... We notice this because all our mapi clients got an error saying that Outlook was contacting the server and it just freezed. ...
    (microsoft.public.exchange.admin)
  • LDAP Bind
    ... LDAP Bind was unsuccessful on directory for distinguished name ''. ... Directory returned error: error code 0x51 Server is not available ... We notice this because all our mapi clients got an error saying that Outlook was contacting the server and it just freezed. ...
    (microsoft.public.exchange.admin)
  • RE: libiconv.la
    ... Subject: sshfs/nfs cause server lockup ... atapci0: port ... cleaning up the object tree ... *** Error code 1 ...
    (freebsd-stable)
  • Re: Deseperately Need Your HELP!
    ... server and all exchnage services are fine. ... The error *sounds* like it could be an issue with the Computer Account. ... Error code 0XC0070574: Logon Failure: The target ... name is incorrect. ...
    (microsoft.public.exchange.admin)
  • Re: Sharepoint Portal Server issue post-SPS SP2
    ... FrondEnd Server + SQL Server ... Context: http://intranet/ Application, Portal_Content Catalog ... at Microsoft.SharePoint.Portal.Data.a.c(SqlCommand, Boolean) ...
    (microsoft.public.sharepoint.portalserver)