I have been testing all evening on both portals, one is version 435, and one is version 335.

Both DNNportals are installed with latest ADfix for appropriate version of DNN.

Both portals have same settings in Authentication module with windows auth. and sync and check ok for the domain.

In IIS6, both portal sites are set for Integrated Windows Authentication only (anonymous is unchecked).
 

This web.config line is uncommented in both versions:
      <add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" />

This web.config line in both versions is :
<!-- Forms or Windows authentication -->
    <authentication mode="Windows">

The web.config lines below are also the same in both versions, they are commented out. 
<!--
      <identity impersonate="true"/>
      <authentication mode="Windows">
      </authentication>
  -->

Both versions have several DNN Security Roles manually created by Superuser acct in this format: MYDOMAIN\secgroup. These roles are exactly same as pre-2000 group name in AD. I have checked with ADSI Edit, and they match starting with: CN=secgroup, ....and so forth.

Issues still encountered:

1. any user that has not been created in DNN previously (meaning either entered manuallly by superuser acct or when the web.config is in Forms authentication mode), tries to access the Windowssignin.aspx page and gets thrown into a loop (the page never loads), and cannot login.

2. Security Roles that I have created to match AD are still not automatically synchronizing for users when they autologin to the Windowssignin.aspx page. Does this take some time to sychronize with AD or is it just not working? How to force synchronize if it is slow? I need to get this working so when users access they automatically get put in the Security Role that matches AD.

Thank you for providing ADfix for the community. Anything you can suggest to troubleshoot issues above will be most helpful.