Re: Unable to bind.
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 26 May 2006 10:35:58 -0500
Are you sure the user has a valid password and is enabled? Those two things
often prevent binds from working.
You can also use the UPN or displayName as a username for binding if you
have set them. That might make it easier than dealing with the full DN.
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"Kevin Crowley" <KTITFM@xxxxxxxxx> wrote in message
news:1148587352.945643.29070@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Update: All of a sudden, it changed error messages so now I'm getting
52 (0x34) Unavailable, errors in LDP. The same situation still exists
with ADSIedit.
.
- Follow-Ups:
- Re: Unable to bind.
- From: Kevin Crowley
- Re: Unable to bind.
- References:
- Unable to bind.
- From: Kevin Crowley
- Re: Unable to bind.
- From: Kevin Crowley
- Re: Unable to bind.
- From: Kevin Crowley
- Unable to bind.
- Prev by Date: Relocate Exchange 2003 and DC
- Next by Date: Re: Number of servers??
- Previous by thread: Re: Unable to bind.
- Next by thread: Re: Unable to bind.
- Index(es):
Relevant Pages
|