For some reason DNN and ZoneAlarm does not get on. You can't login (I guess DNN doesn't test for cookies before login and warn you?). DNN is running on IIS on a XP localmachine.

If I add localhost to the exclusion list (or "site list") still no change in behaviour.
BUT if I switch off Cookie control and ad blocking in zone alarm (it has to be both) DNN starts to work again.

So two questions...

Shouldn't DotNetNuke detect to see if cookies work before it gives you a login screen, and advise you what you need to do if if cookies are blocked? Perhaps the login can be made to work with cookies disabled?

Has anybody managed to get DNN to work with zone alarm cookie control and ad blocking enabled? How did you do it? I'd like to switch it back on.

Many thanks

Alex

Hi Gavin

I can't say, the only app I have that uses authentication (cookies?) is on this PC. One thing I can say, I have no problems logging onto sites on the internet, including dotnetnuke.com. Excluding localhost from ZoneAlarm's privacy won't work either, nor the local IP address. Privacy (cookies) and banner ad protection just has to be disabled.

Any further ideas on how I can configure ZoneAlarm here?

Cheers

Alex

Hi,

I am experiencing the same problems, so if you have found a solution I would like to hear about it.

Thx

Alex coomans