Doh! I responded and my post got whiped out. So here is the quick answer. CHeck to see if users are logging in under www yoursite com and navigating a yoursite com link. Or vice versa. As the login cookie is only good for one and you will appear logged out if you click on a link not matching. So if I logged into this website as dotnetnuke.com instead of www.dotnetnuke.com and clicked on any links referring to posts in the forum they all would show me as logged out I think.

This is just one suggestion and there are many more as I'm guessing you read same posts as I did.

Jason

Another common cause of this is not having the portalID or tabID passed into URL string. This would be something a custom module may do wrong.

To help us out, letting us know what details would help such as DNN version, custom modules used and when users get logged out (for instance perhaps when using a custom module). Also, if a user gets logged out are they truly logged out or just temporarily lost the login state. That is, if they return to a page again and browse around do they get logged back in?

There was a bug fix around 3.0.13 sometime which addressed one logout scenario that I can remember involving portalID.

Can you reproduce it on localhost? Any errors in the DNN exception logs? Anything else strange in the exception log? Anything not normal running in the scheduler that could cause problems? Do you have a high traffic website or not? Are users getting logged out as they are actively browsing or does it happen after they are on a page awhile and then click?

Jason