Re: ADSI Query to filter out machine accounts in the domain

From: Prasad Karunakaran (prasadkkn_at_hotmail.com)
Date: 03/12/04 

Date: 12 Mar 2004 07:32:07 -0800

Marc,
  Thanks for your reply. In that case can I use LDAP Provider instead
of WinNT provider to enumerate group objects, filter out machine
accounts for both a NT domain and AD domain. To be specific does LDAP
Provider support NT domains?

regards,

Prasad

Marc Scheuner [MVP ADSI] <m.scheuner@inova.SPAMBEGONE.ch> wrote in message news:<g9s2505cebf3spbio94nsf17081b6sdhon@4ax.com>...
> > I tried the code you proposed. The code works great with AD. I use
> >the LDAP provider ("LDAP://DomainName") in the domain path when I
> >create the DirectoryEntry() object.
> >
> >I tried using the same code for a NT domain. I changed the provider to
> >WinNT ("WinNT://DomainName") in the domain path and use a domain user
> >account while creating DirectoryEntry() object
> >
> >I get an expection in the following line
> >The exception message : "The provider does not support searching and
> >cannot search WinNT://corp.aspentech.com"
> >Error Code : 0x80131515
> >
> >How should I change the code to work for a NT domain ?.
>
> In short - you can't.
>
> From the MSDN docs:
>
> "Use a DirectorySearcher to search and perform queries against an
> Active Directory hierarchy using the Lightweight Directory Access
> Protocol (LDAP). LDAP is the only system-supplied Active Directory
> Service Interfaces (ADSI) provider that supports directory searching."
>
> DirectorySearcher does *NOT* support WinNT.
>
> Marc
> ================================================================
> Marc Scheuner May The Source Be With You!
> Bern, Switzerland m.scheuner(at)inova.ch

Relevant Pages

  • Re: Need to read "Store password in reversible encryption for all users in the domain"
    ... I always avoid the LDAP provider like the plague. ... as well as servers in domains. ... You can use these filters in ADUC. ...
    (microsoft.public.windows.server.scripting)
  • Re: MOSS My Sites for non-AD users
    ... and I have tried LDAP and AD providers. ... LDAP provider. ... profiles imported with the AD import to accounts created with the ... I'm nearly entirely sure it won't work for forms authentication. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: LDAP Authentication
    ... What matters is the backend LDAP store you are trying to use. ... The membership provider framework is extensible, so you could write your own LDAP auth membership provider that is coded to work with Sun One. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: LDAP Authentication
    ... One of the things with the membership provider framework is that you don't actually have to implement every single interface member when building your provider. ... Most of the complexity stems from managing all that stuff and figuring out the LDAP details to make that work on your given directory platform. ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ADSI Query to filter out machine accounts in the domain
    ... Active Directory hierarchy using the Lightweight Directory Access ... LDAP is the only system-supplied Active Directory ... Service Interfaces provider that supports directory searching." ...
    (microsoft.public.dotnet.languages.csharp)