Windows authentication and Domain

I struggled witrh this a couple of hours until I realised that you can do nothing with session_end or the Global.asax.cs and this is really only intended for system cleanup or creating triggers etc. After timeout occurs all session varibles are destroyed regardless if the user is still got the page on the browser. If the user clicks on a button after session timeout the a new session is created, THIS IS HOW YOU SOLVE THE PROBLEM BY LOOKING FOR A NEW SESSION START. Since session starts should only occur in your startpage (default.aspx mostly) you can watch if a new session starts outwidth this start page by using the Session.IsNewSession = true in the page_load and put a redirect or re-init sessions if required. WARNING: If a user links to page with the below code they will be flung to the start page instead of the intended linked page (sometimes an advantage) ; if this is a problem then discard session varibles use good old Response.Query strings. Simplistic C# for redirecting to default.aspx page. private void Page_Load(object sender, System.EventArgs e) { // Check to if Session has timed out///// if (Session.IsNewSession) { Response.Redirect("default.aspx"); } Hop this helps

when authentication mode="Windows" then how to redirect to default page after timeout? I tried response.redirect in Session_end in Global.asax.cs but not working properly? Thanks in advance

all session variable remain the same in ASP.NET. All you need to do is look up the syntax for Request.SessionVariable("HTTP...") in C#. -James

Anyone?