• I have the latest AD Provider installed
• This was working prior to a 4.8 upgrade.
• Intranet Portal

Now when a new user accesses the portal, it shows "Website found, waiting for reply" but never returns a page and the user is never created.

I had this problem appear about a month after a 4.8 upgrade (im not sure if it was related) so I upgraded to 4.9 to see if it would be resolved but unsuccessful. Sometimes there is a slow comunication process from our remote sites, and new employees come in waves, so it is possible the problem occurred immediately after the 4.8 upgrade.

If I manually create the user in the database, the user can successfully authenticate and access the portal. That leads me to believe that the user creation process is failing in the AD provider.

<identity impersonate="true"/>
<authentication mode="Windows">
</authentication>

<anonymousIdentification enabled="true" cookieName=".ASPXANONYMOUS" cookieTimeout="100000" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="None" domain="" />

<authentication defaultProvider="ADSIAuthenticationProvider">
<providers>
<clear />
<add name="ADSIAuthenticationProvider" type="DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider, DotNetNuke.Authentication.ActiveDirectory" providerPath="~\Providers\AuthenticationProviders\ADSIProvider\" />
</providers>
</authentication>

Those are the sections in my web.config dealing with authentication. I did have have a problem originally with the auto-login but I disabled anonymous access on the virtual directory and everything started working.
 

If I switch to forms authentication, it allows unauthenticated DNN users (still authenticated via windows by virtual directory) to access the site.

I will switch to forms, delete a users ID and have them try to login through the login control to see if they are created. I'll report my findings

Thanks for the quick response.

Jeremy B.

Jeremy, do you still get that error (the critical one) or was it a one time thing?