I am having an issue with the Active Directory module.  We are using windows authentication and are unable to authenticate certain users.  I am a host (user level) on the instance and am able to successfully log in, but when I attempt to log in with a regular user's account, the page gets stuck in a continual loop.  We have run a packet sniffer on our local dc and it shows us that it is communicating with the DC but not performing the LDAP lookup.  When I run it as a DNN host account I see the communication take place, along with the LDAP traffic.  We have tried many different configurations within IIS - all producing the same results.  We have also tried altering the "non-host" dnn account (regular user) by elevating their permissions to a domain admin, etc.  Still no luck.  We will be happy to provide the results of our traces...any thoughts?

What happens when you use Forms Authentication?

We actually tried that yesterday afternoon and thought it resolved the issue, but it did not.  We changed the web.config back to use Windows authentication and it worked for a short while, but we then began to see a lot of these errors in the application log:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date:  12/19/2007
Time:  12:13:02 PM
User:  N/A
Computer: SERVERNAME
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 12/19/2007 12:13:02 PM
Event time (UTC): 12/19/2007 5:13:02 PM
Event ID: 87747b38710e49a7b45f9ba380fd5fe0
Event sequence: 10135
Event occurrence: 618
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/5/Root-1-128425496412737500
    Trust level: Full
    Application Virtual Path: /
    Application Path: X:\..\..CBInside470\
    Machine name: SERVERNAME 
 
Process information:
    Process ID: 3656
    Process name: aspnet_wp.exe
    Account name: SERVERNAME\ASPNET
 
Exception information:
    Exception type: HttpException
    Exception message: Request timed out.
 
Request information:
    Request URL: https://www.cbinside.com/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx?tabid=36
    Request path: /DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx
    User host address: 000.000.000.000
    User: Domain\JQPublic
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: SERVERNAME\ASPNET
 
Thread information:
    Thread ID: 35
    Thread account name: SERVERNAME\ASPNET
    Is impersonating: False
    Stack trace:
 
 
Custom event details:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date:  12/19/2007
Time:  11:54:02 AM
User:  N/A
Computer: SERVERNAME
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 12/19/2007 11:54:02 AM
Event time (UTC): 12/19/2007 4:54:02 PM
Event ID: d690d0d8a8d540f99da3d602ba8f79ac
Event sequence: 7429
Event occurrence: 496
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/5/Root-1-128425496412737500
    Trust level: Full
    Application Virtual Path: /
    Application Path: X:\..\..\CBInside470\
    Machine name: BALHOMESRVWEB
 
Process information:
    Process ID: 3656
    Process name: aspnet_wp.exe
    Account name: SERVERNAME\ASPNET
 
Exception information:
    Exception type: HttpException
    Exception message: Request timed out.
 
Request information:
    Request URL: https://www.cbinside.com/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx?tabid=36
    Request path: /DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx
    User host address: 000.000.000.000
    User: Domain\GLyons
    Is authenticated: True
    Authentication Type: NTLM
    Thread account name: SERVERNAME\ASPNET
 
Thread information:
    Thread ID: 40
    Thread account name: SERVERNAME\ASPNET
    Is impersonating: False
    Stack trace:
 
 
Custom event details:

Notice that the "Is Impersonating" setting is set to false,  while in the web.config, it is set to true.  We also noticed that some users are using NTLM authentication while others are using negotiate.  Please note that I have replaced all business information in the errors with generic text.