W2k3 Stops Serving ASP Pages When Idle

I've seen a bunch of different posts about IIS stopping the service of
ASP pages. Most I've seen appear to have been ADO/Jet linked,
especially when the server is under a load. That being said, I've read
most of the threads about IIS not serving ASP pages, and this seems
different.

This is a brand new Win2k3, Dual XEON, 2GB RAM server.

Running IIS with one website and Windows Streaming Media Server with
one publishing point, Backup Exec, and nothing else.

The server works perfectly until you stop using it. If it sits for an
hour or so, it stops serving ASP pages. Stopping and starting the
website on it instantly brings everything back for as long as you care
to use the server. However, if you walk away for any length of time,
you'll come back to an unresponsive box.

We've turned off all power management on the NICs, set worker processes
to recycle, etc, all to no avail.

Any ideas or help would be greatly appreciated.

Thanks,

- Brad

It does server static files.

Nothing happens whatsoever when browsing an ASP page. No server error
or anything. In fact, while it's hung, if you stop/start the site, the
page will instantly appear on the client machine. If you don't restart
the site, eventually the browser times out (not the server side) so
there isn't any ASP error to see.

It's as if the browser opens the connection, receives a response that
the page exists, and then just sits waiting to receive the content
until if finally gives up.

We've been restarting by navigating to that site in IIS and clicking
Stop/Start.

Nothing shows in the event log.

Would an IIS thread dump/state help next time it happens?

Thanks for the response,

- Brad