I'm working on a replacement for our public website. I want to accomplish the following with dotnetnuke 4.7.

- public users see our public content without being challenged to logon. public users can register and logon if they want to, we want to use this as a way for them to get to customer support content.

- local domain users are authenticated by active directory and automatically logged in, so they can see private content.

Everything I've tried results either in the public user being presented with an IIS logon box, or the private user having to manually login. Is there a way to make this work the way I want? I know I can do private and public on the same portal using DNN authentication but AD is giving me fits.

Mike,

How secure is the setup at NAIT?  How is the web server set up in the domain?  Is the web server in the DMZ?  I'm very interested in seeing how NAIT has set this up between their intranet and the public Internet.

My company would like to do exactly the same thing as the Original Poster, but the IT folks will not allow the the DMZ'd web server access to the Active Directory.  This is also the reason why I continue to ask about the LDAP auth provider, as that would be a good workaround (port 389 is not blocked).

Thank you for any help!

If it helps with your design questions, here is how I have it setup here:

The IIS server is on the internal network, and is part of the Domain. 

An ISA server sits on the Internet and the Internal domain, and functions as a publishing firewall.

The web server is published to the Internet through the ISA server.

Public (Internet) users can browse the website free of any login prompts.

Domain users can browse the website without logging in, and if desired they can click on one button and they are logged on using their domain account.  Note: This will change once the next release comes out, which will allow us to use auto-login.