Thanks aye-jay. I didn't realize until just now that I could click on the Success link and actually see what status code was returned. I was expecting a Failed or some other indication that it was redirecting or whatever.

Anyway, when I looked at my test AD site at home.... It's showing a 302 Found designation but is also saying that it's trying to go to WindowsSignin.aspx. On that site I have trying to authenticate everyone. However, on our school site I've set it up so that only if the IP is from within the local network does it try to authenticate. On those reports I'm still getting the 302 Found designation but links are exactly the same.

So I think turned off the provider on my home site. And got the same results that you did (200 OK).

At this point, I don't think there's anything I can do to solve the problem and still have automatic logons. When the provider is enabled it uses an httpModule (the line in the web.config is what loads it). There has to code somewhere in the core that does the check if the provider is enabled or not and if it is then it loads the module. And that must be where Googlebot (and other site indexers) must be picking up the redirect and there's nothing I can do about that as it would require a core code change.

So what can you do? It depends on how much work you want to do and how big your site is. What I've done (on parts of my portal) is made all pages visible to all users but on pages that are going to contain information that I only want users to see I've put a link to WindowsSignin.aspx. If they happen to be on campus but have logged out of the site for some reason they can click the link and it'll automatically log them in. If they're off site they have to log in manually using the DNN Login link. You can see what I mean @ http://www.bus.nait.ca/Resources/IDrive.aspx. The module that contains the text to login is visible only to UnAuthenticated Users while the rest of the modules are visible only to Authenticated users.

In the meantime I'll try to dig through the core code this weekend to see if I can find where it's doing the redirect to the HttpModule and maybe I'll see something I can take forward to the Core Engineers.

Ok, I`m clearly missing _something_ here... Would be happy, I think, with the set up you use in the link above, Mike, but can`t get it to work here, unless I am misunderstanding what is happening... Does your page (http://www.bus.nait.ca/Resources/IDrive.aspx) not have the Googlebot redirect error?

As the link you have for un-authenticated user links to "http://www.bus.nait.ca/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx" it seems to me that you _must_ have the active directory authentication enabled. (disabled, if I link to WindowsSignin.aspx, I get Windows authentication errors regardless, it seems, of what I set in IIS).

And it doesn't seem possible to use the AD authentication on just certain pages/areas, it's all or nothing.

Basically:
active directory authentication "on" - redirect error
active directory authentication "off" - no redirect error but no authentication

Burned a lot of cycles on this, think I'm giving up... can _not_ tolerate the re-direct, so will either use the DNN login and provide a single set of credentials for the intranet area or maybe look at a separate portal for the intranet side...

Thanks for your time, Mike, anything else you can think of I should try I'm all ears.

aye-jay