Greetings:
Ok, I know the .NET framework is supposed to make things easier, but at this
point, I am rapidly getting the impression that .NET stinks compared to ADSI
when it comes to interfacing with AD through IIS....
In general, can anyone help me figure out how to debug connectivity issues
to my domain when attempting to use System.Directory Services in a web
page???
I have found numerous posts on the net of other individuals having similar
problems. Most of them seem to be discouraged by the uninformative nature
of the errors, and the lack of cross-referenced information about how the
class expects the LDAP connector to be formatted. For instance, do I need
to connect to LDAP://dc=domain,dc=com, or should I be using
LDAP://server/RootDSE?
Obviously, there are many who know how to make this work, but the amazing
amount of people who simply respond with only which namespace to use has
become not only arrogant and condescending, but incredibly discouraging
about the technology as a whole.
So, if you do know how to make Active Directory queries work using the
System.DirectoryServices namespace from an IIS 5 web server on a domain that
does NOT distribute information to anonymous users, and you DO want the
security context to be that of the user who is actually viewing the web
page, I would greatly appreciate some detailed information on how to make
secure AD queries from an aspx web page (without coding a username and
password into a web.config or machine.config file). MSVPs!!! Please renew
my hopes for .NET!!!
Thank you in advance.
Keith C. Jakobs, MCP
