ADAM Authentication Failure

We have an application which queries ADAM (userProxy) for AD authentication,
however in between we have problems where users cant get autheticated for
reasons unknown. When tried to login using ldp, we get an error "Error
49:ldap_simple_bind_s{} failed:Inavalud Credentials
Server Error:Empty

Not sure whats going wrong...it suddenly stops working. Can you tell me what
to look for?

Check and see if the event log on the server has more details and also, if
LDP provides a longer error code, that would be helpful.

The first obvious thing to look at is whether the username specified in the
simple bind operation matches a valid username on the userProxy. Depending
on how the proxies are provisioned, this could either be the full DN of the
proxy or the displayName or userPrincipalName attribute values on the proxy.
Note that these are not necessarily the same values in the matching AD
object so this can be confusing.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Carl" <> wrote in message
news:...
> We have an application which queries ADAM (userProxy) for AD
> authentication, however in between we have problems where users cant get
> autheticated for reasons unknown. When tried to login using ldp, we get an
> error "Error 49:ldap_simple_bind_s{} failed:Inavalud Credentials
> Server Error:Empty
>
> Not sure whats going wrong...it suddenly stops working. Can you tell me
> what to look for?
>