Troubleshooting interrupted Telnet connections

["James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>]

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?

--
JHHL