I am experiencing this same problem in the same scenario.  I am also experiencing this in 2 other scenarios.

1- if the other ASPX page is opened within an IFrame on my portal
2- with no custom modules, no aspx pages.  just normal use!  refresh anywhere in the site a couple times, and POOF, logout!

Core team... anyone... whats the deal?  Thanks!

This is not a bug, but is a side-effect of calling an ASPX page directly without having one of (1) the child portal's folder, or (2) a tabid querystring param, or (3) a mid (module id) querystring param in the URL. Since the portal detection code cannot detect which portal the request is for it results in the current login being terminated.

If you modify the URL to include a querystring param of tabid=XXX (XXX being the ID of a page associated with the child portal), this will work (example: http://yoursite/somepage.aspx?tabid=123)

Nik

right, I understand.  But what about the case where there are no ASPX pages called?  only the normal use of the portal, and refreshing a page such as this?

http://localhost/MyDNN/Home/tabid/53/Default.aspx

This is a valid url, which, although doesn't say tabid=  or portalId=   it does have the alias, tab info, and all the necessary info in the URL  (which should get translated properly by the DNN internals).

I still get logged out from a refresh or two in this case.  I find that to be odd, and my users would too I think, which consitutes a "bug" (any unexpected behavior).

Does anyone have any input on this matter?  This can't possibly be affecting just me.  I am experiencing a serious logout problem on DNN 3.2.1 and 4.0.2. 

I am experiencing the problem under all circumstances listed above, but also on pages with NO custom controls or modules.  I can create a blank page with no modules, log in, navigate to that blank page, click Refresh once or twice, and POOF, I'm logged out.

I'm also experiencing spontaneous logouts navigating my site generally.  most especially prevelant when I go to edit mode on a module.

I also just discovered that portal 0 doesn't seem to be affected for whatever reason.  But all other portals have the issue.  I also discovered that the issue apparently does not happen to the Host super user, but only other users of any other type who are logged in. 

The worst of this is not so much the refresh issue, but is the fact that if I navigate to the "edit" mode of a module and the back out, it logs me out.  This is an absolute show stopper for me.  It appears to happen only to modules I created using the starter kit.  On the other hand, the refresh issue is everywhere site wide, regardless.

This is just whacked.  It has got to be a DNN bug.  Why is there not more buzz on this topic?  I've scoured google.