Problem med LDAP i webapp

Ingen svar - så jeg lukker.

Har dog opdaget et spm. http://www.eksperten.dk/spm/638634

Problemet løst - jubii...

For at andre ikke skal lede i i flere uger som mig er her en "løsning":

På http://www.codeproject.com/csharp/arbauthentication.asp findes koden:
------------------------------------------------------
public void Login()
    {     
      // now create the directory entry to establish connection
      using(DirectoryEntry deDirEntry = new DirectoryEntry(this.strDomain,
                                                          this.strUser,
                                                          this.strPass,
                                                          this.atAuthentType))

      {
        // if user is verified then it will welcome them
        try
        {               
          MessageBox.Show("Welcome to '" + deDirEntry.Name + "'");
         
          // TODO: add your specific tasks here
        }
        catch (Exception exp)
        {
          MessageBox.Show("Sorry, unable to verify your information");
        }
      }
    }
------------------------------------------------------
Koden skulle gerne være følgende:

DirectoryEntry("LDAP://MYDOMAIN", "cn=username", "password", AuthenticationTypes.Secure)

Hvis dette ikke virker kunne følgende tråd være en hjælp:
http://www.dotnet247.com/247reference/msgs/36/182022.aspx - se sidste indlæg

I tilfælde af at det forsvinder er en lille del af svaret her:
-------------------------------------
Solutions:

The solution is to run your ASP.NET application under an account that can
access AD. There are a couple of ways to do this:

1) You can actually do all your work WITHOUT sending a username and password
to the DirectoryEntry bind if you're running under the system account. This
isn't an anonymous bind, it's a privileged one, because you can actually
search the whole AD tree (an anonymous bind to AD gives you almost nothing
to look at)

e.g. DirectoryEntry entry = new DirectoryEntry("LDAP://DOMAIN");

This isn't an option for me, as I need to bind with the username and
password as a form of authentication.

2) Ensure ASP.NET runs under the MACHINENAME\ASPNET account by setting the
userName attribute in the processModel section of machine.config to
"machine" (make sure the password attribute is set to "AutoGenerate"). This
will enforce the change on all ASP.NET apps. This is recommended as using
"system" is insecure and essentially "deprecated".

3) Run your specific web application under a specified username and
password, such as a domain login. Do this by adding the following line to
web.config:

<identity impersonate="true" userName="DOMAIN\myusername"
password="mypassword"/>
</system.web>
</configuration>

Troubleshooting:

1) First you should test that you can actually get to the Active Directory
using the LDAP method by using a standard LDAP client such as LDAPBrowser
2) You should make sure the username / password you're using can actually
bind to the AD using the LDAP Browser
3) Use the line of code a bit further up to troubleshoot what account your
app is running under (i.e. to see whether your impersonation or
machine.config changes have taken effect)

I hope this helps you! Was a frustrating error that had no documentation or
solutions I could find.

Tak