Hey dbsboy, 

I started this thread and watch all the messages, just to see if someone resolves this problem.  The best advice/solution I came away with was to find a new host.  Brinkster's servers must have a peculiarity that causes the problem, although they won't admit it.

Since I went to WH4L, I've had (almost) no problems with any of my website, and NEVER suffered a spontaneous logout.  I also have DNN on my dev server, but have not been able to re-create a condition that causes the problem on that installation.

If you have patience and like a challenge just hold out for a solution.  But if you want your DNN site up & running quickly, change hosts.

Thanks much for your advice rickla1, I'm seriously considering switching host now.

Unfortunately my brinster account has been over 10 months already. Would you happen to know what's the penalty fee for cancelling the account early?

Charlie

I just setup DNN 3.2 using a two server web farm with a backend db server (Windows 2003 network load balancing cluster).  I am also getting the spontaneous logout problem.  Is there any resolution for this?  I see from other posts that DNN doesn't use sessions, then why does the logout happen.  In addition, the only person I saw that has successfully used the web farm support used "sticky sessions", but DNN doesn't use sessions?

Someone said to disable "http authentication", where is this exactly (IIS, web.config) ?

Any help is appreciated.

Cathal and rickla1,

I'm having a similar problem, however I don't believe it's related to sessions.

I just experienced this problem with DNN 4.0.2 on WH4L (WebHost4Life) as well.  I've now had this problem on 4 hosters.

Like others, I'm having problems with getting logged out of the child portals.  However, this problem happens intermittently and when it happens, I get logged out only after I go to any of the following:

- Settings page for any module

- Edit User Account page

- Register page (the page I get when I click on my username)

- Page Management page (the page after clicking on "Add", "Settings", "Copy" in Page Functions)

after going to any of the above, then clicking on any other link will log me out.  (Also, the "update" link on the above pages do not work during these intermittent times.  An "error on page" message appears on the bottom bar of the browser.)

(there might be other places I haven't found yet that causes the log out)

If I don't go to those places, such as going to different tab pages or Preview (under Page Functions), I will not get logged out.  I can edit the text in the Text/HTML module and I will not get logged out.  Therefore, my session is still active.

This just happened at http://aspdotnetnukehost.com .  This is a barebone DNN 4.0.2 site that websecurestores.com (hoster) set up for demo purposes.  We did not add any modules.  I created a "test" child portal:  http://aspdotnetnukehost.com/test and without adding any of the DNN modules to what's already there (based on personal template), I experienced the problem.  You can log in:

username:  test
password:  test

Because of this problem happening with this barebone portal, I'm surprised that I haven't come across anybody else's posting that mentions this problem.

This intermittent problem happens even when there is NOT an application stop and start.

Therefore, I don't believe this problem is caused by any hoster.  I think it's got to be with DNN.

Does anybody know what is causing this problem?

This is incredibly frustrating as I've spent 2 weeks on this, going from hoster to hoster and scouring the forums.  This problem would render DNN to be useless for child portals.

In addition to my previous post, I've also tried this with 2 PCs, so I don't think the problem is caused by my PC settings.

Unfortunately, both PCs are running Windows XP with IE 6.

I have also been experiencing this problem with DNN 3.2.1 on my own production server (Win2003). I have posted to the various forums including DNN (http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/12115/threadpage/1/scope/posts/Default.aspx), logged a bug in Gemini (DNNP-2546), and have yet to have anyone (except the numerous users having the same problem) acknowlege this issue. I have one portal, no child portals and a few additional modules by SMcculloch (a core team member) and ActiveForums 3.5. Any and all users are getting logged out with no repeatable process to cause this.

I have another site running DNN 3.1.0 with all these same modules installed and have never hag a problem with spontaneous logouts. This suggests that the problem is not with the browser, but with any version of DNN modified for ASP.NET 2.0. I will upgrade to 3.2.2 in hopes that this will fix this problem.

I am baffled that this major usability problem has been hanging out there for so long now, with seemingly limited interest by the Core Team. If this problem cannot be resolved, DNN truly becomes a legacy application and can no longer be used for its intended purpose.

As you can see from my previous post there are some serious repercussions when using FireFox and Google spell checking in both the ASP.NET forums and the DNN text editors.

I installed DNN 3.2.2 in my dev environment (Win XP) which has been experiencing the same spontaneous log out as my mentioned production site, and still have the same problems.

I have a production server running Windows 2000 and SQL Server 2000, all installations are running DotNetNuke 3.2.2;  One of the DNN installations spontaneous logs out User A, but another DNN installation with the same configurations does not log out User A.   When I log into the server, as host or administrator, to recreate the same problem, it doesn't log me out... everythings works like a charm.  Nor does it log me out using User A's credentials.

I do hope this gets resolved sometime soon.  I went through the effort to upgrade everything to 3.2.2 to make this go away, but the problem persists.  User A has disable all Norton Antivirus software-- but obviously the software is pushing them back out to the login screen to get credentialed.  This issue may have started in v3.1.1