I'm having a strange issue where, on a fresh install, I login as host, attempt to make a change to the Host Settings, and get asked to log in again. When I do, I'm back at the home page, click on Host Settings, and get asked to log in yet again. It seems DNN isn't remembering when I log in.

I've experienced the issue on my public web server, but not on my local development server, which leads me to believe there may be some kind of configuration issue between the two machines. The server which is suffering is Windows 2003 Server w/ SP1, running on IIS6 and .NET Framework v1.1. This machine also has .NET Framework v2.0 installed, but the site i'm running DNN in is configured only to use v1.1.

The local server is also Windows 2003 Server w/ SP1, also on IIS6, but with only v1.1 of the Framework.

Is it possible that the issue is being caused by a v2.0 misconfiguration? I had a similar issue with a site under 2.0 which would not remember logins. This issue has now been resolved, but I can't put my finger on what solved the problem.

I've been able to produce the problem on v2.1.2, 3.0.12, 3.0.13, and 3.1.

Are you running Zone Alarm, or some other kind of privacy/cookie blocking software on the machine?

Nope, nothing of the sort. It doesn't even work when I look at the portal using a browser on the webserver via Remote Desktop. If you want, I can give you the host account details to try yourself?

Has anyone else managed to get this to install successfully on a Plesk based server?

I am using a Plesk based server and DNN1 used to wrok on my server at home but since moving to my hosting company it no longer works.

Is there something in Plesk (which I know nothing about) that is stopping it from working?

it's a breaking change in asp.net 2.0 -I blogged about it http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/233/Default.aspx , you'll have to change the forms authentication timeout.

Cathal

I  have checked and I am using ASP 1 not 2.

My hoster says he has been on some forums and other people are having this problem, but his final word is "we don't know how to fix this"

Can anyone offer some more things to try.  Is it possible there is a problem with the Plesk setup?

I have read a few posts and have tried:

Cleared the site log
Added the timeout in the web.config   
Cleared my local cookies

All with no success.

Please someone help, my members are complaining, plus it used to work when I hosted at home.

Thanks

Simeon.

I don't have any great insite just what worked for me on 3.1.1. I had a bad module that logged my user out whenever they tried to edit it and it was also related to allowing multiple worker processes on a machine that was supporting multiple portals.  Like I said, no great insights and it may not even relate to your problem but it's what worked for me.