Hi Jon - I think part of the confusion is in the wording we both may be using. 

By testng this Portal to portal I am setting this up and testing on:

• different child portals from the same parent on one SQL and web server(they are on separat boxes)
• different parent portals on the same webserver (same SQL server)
• different parent portals on different physical web servers (QA web server and DEV web server boxes)

In all cases, I have used the same exact settings for my domains and it works fine in all directions. 

My setup is as follows:

1. All servers are Win 2003
2. SQL Server 2000 - all using the same SQL box, but different DB's, so they could be anywhere
3. IIS6.0
4. DNN 4.02 & 4.03
5. Using the following settings in Authentication:
   1. Win Auth checked
   2. Synch role checked
   3. ADSI Provider (default)
   4. Auth type - delegation (default)
   5. Root domain - set for your domain
   6. User name - cn=*username*,ou=*org unit*,dc=*** (user should have domain priveleges across all domains required)
   7. passwords
   8. email - blank

I have tested this across the different portals using all of our domains and it works fine.  What exactly are you experiencing? 

I'll happily document as best possible - provided I can fit in the time.  I do not understand what you are alluding to in teh "more than one SQL database", as that to me implies you are speaking of a different issue of some sort, rather than end users going from one domain portal (edited) to another. 

Realize - I am also reporting result from a PC joined to that domain, and while I have administrative rights, I have succeeded with using a non-admin account on other domains.  You might also contact the server admins to see if any other restrictions are in place preventing the asp.net application from being trusted to check the ad info. 

Have you tested with other auth settings on teh model - such as readonlyserver? 

Are you testing with an actual ad user - dumb question I know - but I checking to see that you are not expecting DNN to add a new registered DNN user to AD, and propagate to the other sites.  I've seen this asked in the forums before.  Users must exist in AD first, not the other way around.  

Let me know specific test scenarios you are failing on and I will try to assist.  Detail this as best possible - especially any part about the server environment (hosted, internal, home, etc.)

Cheers

 

 

I'm working on some screen captures to show the setup & functionality.  Give me a week or so - as I am rolling out a beta/QA portal for my staff and two pilot sites and am a bit consumed. 

See my other post here for some issues I have run into (with auto-login and applying a LANIP mask):

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/89/threadid/18959/scope/posts/Default.aspx

 

Did you create the same roles in other portals before logging into them using the AD account?  I never had the problem on any admin account across portals, only in DNN roles created afterwards.  Do you belong to the "administrators" group in AD?