Hi Tam

I have installed the release 3.2.0, and it´s working great.

I wonder though if You have removed the ability to use "AutoLogin" when using Active Directory Authentication. I am using the module for our Intranet, and the users would appreciate avoiding logging in each time they start the Intranet portal.

Cheers

Sveinur

When I set up under Admin/Authentication in DNN32, I get this:

Accessing Global Catalog:
OK
Checking Root Domain:
FAIL
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
The specified domain either does not exist or could not be contacted

If I try to add the domain and user account, the GC access fails as well.

I have had mixed results; used Windows authentication and added user automatically but want to used mixed - Forms. I can log on as host but not with an AD account, whether user exists already or not in DNN. I switched the IUSR to a valid AD account for the WindowsSignin.aspx file.

Here are the errors I see in the log when the AD user login attempt fails:

AssemblyVersion: 03.02.00
Method: DotNetNuke.Security.Authentication.ADSIProvider.GetUser
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: SUNY Fredonia
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
AbsoluteURL: /adhome/Default.aspx
AbsoluteURLReferrer: http://ww4.fredonia.edu/adhome/Home/tabid/36/ctl/Login/Default.aspx
ExceptionGUID: 2f12dfbf-d00d-4e78-aad4-12428bd95276
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Object reference not set to an instance of an object.
Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)

AssemblyVersion: 03.02.00
Method: System.DirectoryServices.DirectoryEntry.Bind
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: SUNY Fredonia
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
AbsoluteURL: /adhome/Default.aspx
AbsoluteURLReferrer: http://ww4.fredonia.edu/adhome/Home/tabid/36/ctl/Login/Default.aspx
ExceptionGUID: c657f296-769d-4889-a688-b56012f18029
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: An operations error occurred
Message: System.Runtime.InteropServices.COMException (0x80072020): An operations error occurred at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at DotNetNuke.Security.Authentication.ADSI.Domain.PopulateInfo() at DotNetNuke.Security.Authentication.ADSI.Domain..ctor(String Path) at DotNetNuke.Security.Authentication.ADSI.Domain.GetDomain(String Path, String UserName, String Password, AuthenticationTypes AuthenticationType) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootDomain()

I assume there is a connection between these errors and the two initial FAILS for root domain and LDAP access.

Is this something I've configured incorrectly in DNN (don't think so) or something about our AD set up that is not permitting access?