×
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.
I would start with firewall, VPN concentrators, Routers, and switches logs. Enable Keep Alive packet on the client.
Monitor the iSeries Ethernet Lines.
Check PTF's for TCP group etc.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
thereof. Thank you for your cooperation with respect to this matter.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, April 22, 2010 3:29 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Troubleshooting interrupted Telnet connections
We've long learned to live with having our Telnet connections to our
customers interrupted after a relatively short period of inactivity,
whether by a short QINACTIV, or by some intervening piece of hardware.
In most cases, except with the one customer whose box is set to disable
concurrent sessions, we never have a bit of trouble reconnecting and
picking up where we left off.
But that particular customer is having the same problem with THEIR OWN
remote users (and it's clearly NOT QINACTIV-related), and they've
started blaming US for it.
Anybody know a good way to track down this sort of glitch?
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.
midrange.com
