IIS 5 & IIS 6
Immediate session expiry on login
Last post Dec 02, 2008 09:44 PM by lshields
Aug 21, 2008 11:14 PM|nishad_paul|LINK
I have an application installed on IIS 6.0 with ASP.Net and .Net Framework 3.0, in Win2K3 server. When I login to the application from the server, the process is smooth, and the application moves on to the post-login pages. But, when I login from any other
client machine, the application gives a session timeout alert as soon as I enter login credentials, and puts me back on the login page. I just cannot login from any client.
I have tried changing the security settings on the client browser, to the extent of 'no security'. Still, I don't see the cookies getting set in the client. Now, the question is, whether the cookies are even getting generated and transported back to client
Any solution to this problem?? How can I check if the session token handshake is happening here??
Nov 27, 2008 12:21 AM|tanmayathopate|LINK
You can check following link to fix it. Session time out needs to be set by 2 settings under IIS 6.0
Dec 02, 2008 09:44 PM|lshields|LINK
I know this seems kind of simple but you might want to check the Date/Time on the server vs the Client Machines. I know I ran into something similar with an App where the server set it's clock back 2 years after some Hardware replacements and the cookies
where expiring on the client as soon as they were created.
Also, by default the Session Timeout in IIS 6.0 is usually set to 20 mins. Unless you are overriding this via Web.config, it's probably not timing out.