We are running DNN 5.5.1 on Win 2k3 server, SQL 2005, using AD integration module version 5.0.2, supporting our company Intranet.  The AD integration seems to be working great in the parent portal.  We created a child portal for one of our larger departments, so they could self manage all content in the portal.  We seem to regularly have the problem where when adding a new AD group to the child portal, users are not automatically added to the group in the child portal.  I have confirmed the settings of the AD module in both portals and they are identical.

We hire a lot of temporary employees into this department and thus far have been manually adding them to the AD group in DNN so they can view the appropriate content.  This pretty much defeats the purpose of the AD integration.  Please advise.

We don't think it's happening all the time.  The current scenario I have is a user that already existed in AD and had rights in the parent portal.  I added a new (already existed in AD) group to the child portal and granted this group View rights to a section of it.  This user already existed in the group.  When she goes into the child portal she does not see the new pages to which she should have rights.  We have logged in/out, etc, but not done an App Pool reset yet.  How often does the integration refresh the DNN users tables from AD - is it only when a user is first discovered and created in the portal?

The user is (and was) present in the users listing in the child portal, but has not been auto added to the group that I added (which already existed in AD, I just created the group in DNN) to the portal.

One thing that may or may not be related. All our users have the domain name at the front of their DNN user names (i.e. domain\username). So we can only view them by selecting to list All in user management. This goes way back to our original DNN 4.x and AD integration several years ago.