Paul,

Bingo! Thanks for your help.

Best regards,

Bob


>>Paul,
>>
>>No, I am not updating web.config or overriden anything in the global.asax file. To further test, I changed the session timeout to 1 minute, opened a web page waited 1 minute+ and the login screen popped up. This proves that the setting when changed works sometimes. Then I changed the setting to 25 minutes. I waited 22 minutes and got timed out again, which would suggest that 20 minutes (or thereabouts) is the default being used whenever the setting is greater than this.
>>
>>Have you ever set your timeout to greater than 20 minutes? And if so, did it work?
>>
>
>Yes. I've got my stuff set to over an hour (and an option to not expire). I even did a test with a basic MM.NET project yesterday to make sure this was working the way I'd expect.
>
>However, it just occurred to me - this probably isn't a session issue; I think that's working OK. I bet IIS is recycling the app-pool; it will do that after (I think this is the default) 20 minutes of inactivity.
>
>Go into IIS, expand the Application Pools node. Right-click on DefaultAppPool and select Properties. Make sure Recycle worker processes (in minutes), if it happens to be checked, is set to 120 minutes. Then click on the Performance tab. Change the "Shutdown work processes after being idel for (time in minutes)" to something like 120 minutes. Hit OK. Now retest.