Welcome to ISAserver.org

Website Timeouts

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Website Timeouts

Page: [1]

Message

<< Older Topic Newer Topic >>

Website Timeouts - 17.Dec.2007 4:04:40 PM

tzonarin

Posts: 12
Joined: 25.Sep.2007
Status: offline

I have a single website that I'm hosting through my ISA 2006 server, configured as an edge-firewall. There is one listener for this site, allowing access to both internal and external clients. There is no HTTP authentication set up for the site, since any authentication is handled within the ASP code, which authenticates to the database.

For some reason, my website is getting timed out after five minutes of client-side inactivity, which happens for both internal and external users.

I've checked the timeout on the Web Listener and the IIS website and both are set to 5400 seconds (90 minutes).

I'm not setting any timeouts in ASP for my session cookie, which means it should take on the default of 1200 seconds (20 minutes). I don't suspect anything in my ASP code because this site was incorporated from another server platform and brought in-house.

Over all, it's a pretty simple setup, but not so simple of a problem. I get the feeling that I'm overlooking something obvious. Any ideas, folks?

-Tzo

Post #: 1

Featured Links*

Problem Fixed - 20.Dec.2007 2:29:15 PM

tzonarin

Posts: 12
Joined: 25.Sep.2007
Status: offline

Hey everyone -

OK, I sorted this, but it wasn't my ISA server at all. It was a config issue on the IIS Server.

Turns out, I was operating on the premise that the default session timeout for ASP is 20 minutes. Historically, that's what it's always been. It never occurred to me to challenge this.

Well, in IIS 6.0 the ASPSessionTimeout variable is in the Metabase and is, by default, set to 5 minutes. Since I was using Session Variables, the timeout directly applied to them.

Brought down all IIS services, modified the metabase (since this value is not configurable via GUI), and started 'er back up, presto. Timeout issue resolved.

When configuring Timeouts, remember that there is a timeout for the Listener as well as for the Website. Best thing is to just set all these to the same value so you don't freak yourself out.

So there it is. Hopefully this post will help some other unfortunate chap who may run aground with the issue.

Merry Christmas!

-Tzo

(in reply to tzonarin)

Post #: 2