Re: LDAP Lookup failure
- From: "Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx>
- Date: Fri, 15 Jul 2005 09:02:52 -0400
Mark, what's the application?
A lot of times, if you turn up the audit logging for failed logon attempts,
it's really helpful in determining what credentials are being passed to the
server by the application. You can often narrow it down pretty quickly that
way.
Al
"Mark" <nospam@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23QBBcMSiFHA.1412@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I am not hugely experienced in AD matters, and have had some trouble with
> an application that needs to authenticate against my AD on SBS2003.
>
> On the software I am getting communication and bind errors, when doing the
> lookup. It is a very strange situation, as it works for a while, and then
> with no changes will stop and give the communication and bind errors.
>
> I have also tried using the LDAP browser application, and cannot get this
> to work.
>
> The following settings were used:
>
> Host: server.domain.local
> Port 389
> Version 3
>
> (I can fetch DN's succesfully)
>
> Turned off anonymous bind (should this work with anon?)
>
> User DN: cn=%username%
> Password: %correct password for user%
>
> Thanks for any help advice you can give.
>
> Mark
>
.
- Follow-Ups:
- Re: LDAP Lookup failure
- From: Mark
- Re: LDAP Lookup failure
- References:
- LDAP Lookup failure
- From: Mark
- LDAP Lookup failure
- Prev by Date: Re: AD integrity with applications demanding domain admin rights??
- Next by Date: Re: A question regarding the /3GB Switch
- Previous by thread: LDAP Lookup failure
- Next by thread: Re: LDAP Lookup failure
- Index(es):
Relevant Pages
|