Hello Mike

I've got an intranet (intranet.mydomain.com) that uses your ad-provider. Now we'd like to use the whole system to bring some information to the public (www.mydomain.com), too.

I've set up iis to force authentication if the url is intranet.mydomain.com but not if www.mydomain.com. Unfortunately I can't tell the ad-provider to disable out-logon if www.mydomain.com is used. So whenever I enter www.mydomain.com there is a error-message that sais anonymous access should be disabled in iis.

Any hint to solve my problem?

Thank

Ueli

Hi Mike

I'm using dnn 05.01.01 (98) and AD-Provider 5.0.2

My Users can login form within our network (ip-range) and from home. So the ip-range can't be said.
That's why I depend on reacting to the entrance they take (public.mydomain.com or intranet.mydomain.com)

Hi Mike

It's exactly as you are writing.
So far my useres needed to login via standard-browser login-windows and not the dnn login screen because IIS ist configurated to force authentication.
I'd like to keep that procedure for my domain intranet.mydomain.com but wan't to change it for public.mydomain.com. public.mydomain.com should act like an ordinary dnn-page would do: No forced login but the possibility to do manually.
 

That's why I created a virtual directory in IIS (public.mydomain.com) that points to the same page as intanet.mydomain.com but without foreced login. Unfortunately the ad-provider tries to perform an autologin and spits out an error (plain text message: Error while processing Windows Authentication
Check your IIS settings. DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx should NOT allow anonymous access). This happens only the first time you enter a page. If you then reload the page you can surf the page as an anonymous person exactly they way I want it.
 

Thanks for you help