× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Client Access stays connected
  • From: Patpong Watwanitchakorn <patpong@xxxxxxxxx>
  • Date: Wed, 23 Jun 1999 08:38:53 +0700

I agree with Nina, it doesn't work.  My question is that how to specify both
parms of Telnet Attrib, Inactive Timeout and Timemark Timeout to control the
telnet client as following options?
 
1. Give them 30 minutes for inactive timeout.
2. Recover to any client who failed the connection ASAP.

My current setting, Inactive timeout is 1800 and Timemark timeout is 0,
means that I can control the user who always leave the keyborad for a long
time _BUT_ I can't to recover to any client who failed the connection.  I
did try to combine setup both parms and found that the Inactive timeout
won't work if Timemark timeout is active.

ppw
> ----------
> From:         nina jones[SMTP:ddi@datadesigninc.com]
> Reply To:     MIDRANGE-L@midrange.com
> Sent:         Tuesday, June 22, 1999 7:41 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Client Access stays connected
> 
> >  Use of the Telnet Timemark Timeout (CFTTCPTELN Option 1) should cure
> > your problem.  With the timeout set at 40 seconds the sessions should
> > drop out in under 2 minutes.
> > 
> >  In order for the timeout to work correctly, see the PTF's below and
> > read the coverletter Carefully for application and activation.  The
> > system will detect lost connections quicker and more reliably, by
> > letting the stack do it.  Without these PTF's the timeout appears to
> > be almost totally ineffective.
> > 
> > PTFs by release:
> > 
> >         5763TC1 V3R2 SF53481
> >         5716TC1 V3R7 SF53483
> >         5769TC1 V4R1 SF53485
> >         5769TC1 V4R2 SF53486
> >         5769TC1 V4R3 SF53489
> 
> ah!  no wonder it didn't work.  i tried that months ago, and i'd get
> knocked off while it was active.  thanks!
> 
> nj
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.