I know from searching though this forum that Mike doesn’t have access to a Multi-Domain setup with which to test the provider, so I’m relying on some of you other Active Directory professionals for help.
I have a fairly simple forest with two domains (DomainA & DomainB). The domain and forest functional levels, until recently, were at the lowest Windows 2000 mixed mode with no Universal Groups. I have since updated both domains and forest functional levels to Windows 2003.
Here are the other pertinent system specs
Web Server and DCs are all Windows 2003
DomainA was the first Domain created
Web Server is a Member Server of DomainA
DNN version 5.2.2
AD Provider 5.0.2
The Authentication Provider installed with no errors and after setting it up I got a green check and the two Domains were visible. No Default Domain is set.
I also commented out the <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory . . . line because I don’t want the Windows Authentication Popup as suggested in the Documentation.
Using the DNN Account Login Module (not the Windows Authentication Pop-up) I can login to as DomainA\username but not DomainB\username.
When I try to login to DomainB I get the following error in the Event Viewer
AssemblyVersion: 5.2.1
PortalID: 0
PortalName: SDINet
UserID: -1
UserName:
ActiveTabID: 58
ActiveTabName: Login
RawURL: /Login.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://sdinet2.DomainA.com/Login.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: ce1eb525-517d-49b4-8027-534af48e3623
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser
StackTrace:
Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)
Source:
Impersonation doesn’t matter. I’ve tried it both ways, commented and uncommented with a user from DomainA.
Why won’t the DNN Account Login Module work for DomainB