2003KJ
Member
I've been getting alot of "connection timed out while attempting www.jeepkj.com" lately. Know what the deal might be?
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
nMinutes
Specifies the number of minutes that a session can remain idle before the server terminates it automatically. The default is 10 minutes. Session.Timeout has no hard-coded limit. Most Web administrators set this property to 8 minutes. It should not be set higher than 20 minutes (except in special cases) because every open session is holding onto memory. It should also not be set lower than 4 minutes because clients rarely respond within that time resulting in a loss of session state.
SiLveRLiB2k2 said:hm..
900 seconds?
thats about every 15 minutes...now that i think about it, that sounds about right....i'll keep more of a note, between when the messages appear..
do u have keep alives enabled?
found this interesting bit..
nMinutes
Specifies the number of minutes that a session can remain idle before the server terminates it automatically. The default is 10 minutes. Session.Timeout has no hard-coded limit. Most Web administrators set this property to 8 minutes. It should not be set higher than 20 minutes (except in special cases) because every open session is holding onto memory. It should also not be set lower than 4 minutes because clients rarely respond within that time resulting in a loss of session state.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iissdk/iis/ref_vbom_sesoptime.asp
2003KJ said:It happens for me with more than one browser open (i'm running Firefox), and with just this one. Also, Internet connectiion is Road Runner, speed is up around 2800-3000....not too bad for cable :-k
2003KJ said:Just did mine, up around 2950...not too bad. I've had RR for about 4 years now.