|
John - check the Knowledge Base doc titled V4R4M0 and V4R5M0: Telnet Timemark Time-Out Parameter This explains about TCP keep-alive parameter (TCPKEEPALV) and The Telnet Session keep-alive parameter (TIMMRKTIMO) and how this works with the System Values QINACTITV and QINACTMSGQ. More than I could summarize here. I do know in early V4 there were ptf's to get this right. jim franz ----- Original Message ----- From: "John Taylor" <jtaylor@rpg2java.com> To: <midrange-l@midrange.com> Sent: Tuesday, September 04, 2001 4:47 PM Subject: Re: Client Access Session Drops > Routers are all the same Cisco model. WAN is online 24/7, and is a monitored > service. Devices are active for the duration of your typical 8 hour workday. > The most recent incident occurred this past Sunday, when the user was the > only one on the system, so the number of active devices doesn't appear to be > a factor. > > Ethernet & TCP across the board. Server is currently at V4R5, but I seem to > recall it beginning way back with V4R2. Clients are all CA/Express with > current service packs, but the versions vary from V4R4 to V5R1. Client OS's > include W95, 98, NT and 2K. > > When a session is dropped, the host job remains active with no message or > other indication that anything went wrong. > > I'd call this in to IBM support, but my experience with them is that it's > pointless to do so unless you can provide them with a reproducible test > case. > > > John Taylor > > ----- Original Message ----- > From: "Jim Franz" <franz400@triad.rr.com> > To: <midrange-l@midrange.com> > Sent: Tuesday, September 04, 2001 11:34 > Subject: Re: Client Access Session Drops > > > > depends on how often the devices are active, and since it sounds like > > multiple routers, would not suppose they are all the same. > > have to ask - is this ethernet all the way, or are there sna controllers > > involved (requires some change to controller config for WAN vs LAN > settings. > > Also, what OS Version? > > jim > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.