Re: cant connect to ADAM instance with System.DirectoryServices
- From: "Joe Kaplan" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Sep 2006 12:18:10 -0500
Yes, it is case sensitive. You get a weird and unhelpful error when it is
wrong. I think we cover that in ch 3 of our book if you are interested.
Also, if you are programming in .NET 2.0 and prefer a lower level "pure
LDAP" approach to programming in .NET, you might consider checking out
System.DirectoryServices.Protocols. Both it and S.DS are fine for
programming ADAM. It really depends on what you are doing and what you are
comfortable with, but you have options. There are a few features that you
can only get to using the lower level API though (such as ADAM digest auth).
More details on this stuff at my blog:
www.joekaplan.net
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
--
"scottw512" <scottw512@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4229CA50-3EF8-429E-8DB6-8C222BBD969D@xxxxxxxxxxxxxxxx
I figured this out. The protocol part of the URL (ldap://) has to be
uppercase.
"scottw512" wrote:
Is this supported with integrated windows authentication? The object
constructs ok, but when I try to access a property, I get a stack trace
in
get_AdsObject. The code looks like this...
msde = new
DirectoryEntry("ldap://bwdwpdepl01:389/CN=Pwiz,DC=Brentwood,DC=VCN");
object obj = msde.Properties["distinguishedName"];
I can connect and query over raw sockets using the library at
http://forge.novell.com/modules/xfmod/project/?ldapcsharp, so I know the
ADAM
instance is there and responding.
.
- Prev by Date: Re: Query active directory
- Next by Date: Re: Query active directory
- Previous by thread: Re: 2003 domain - Group Policy problem
- Next by thread: nt4emulator
- Index(es):
Relevant Pages
|