Jeff writes:

> The 3000's telnet *client* has never been terribly robust, although it
>  appears that Wirt's version may have a new edge (which could be due to
>  the telnet client, or the native mode telnet server, assuming that he
>  connected that way).
>
>  There have always been discrepancies with the 3000's telnet client in
>  some combination of configurations, and yes, it used to vary depending
>  on how you were connected in the first place (serial, NSVT, TAC, or
>  native telnet).  IIRC, I could telnet to the Ciscos from our console,
>  with some annoying warnings, but it was workable.  I can't speak for
>  it now as I am rarely around the consoles anymore (I relocated to
>  another building last summer).

We have been on the various versions of the "advanced telnet" patch for
nearly four years now. We have four machines up at the moment, one each
running 5.5, 6.0, 6.5 and 7.0. The telnet code we use, which I get directly
from Jeff Bandle as an SOM patch, is the same on all machines; it is O/S
version independent.

I have found this telnet code (which is still unfortunately not distributed
to the general population as part of a GR release) to be enormously stable
and robust. I've never had a moment's trouble with it.

I would strongly recommend you to get the appropriate patch from the response
center and load it on your machines. (The "appropriate" patch is only
necessary in order to get the version numbers to line up; otherwise, it's the
same code inside in all versions).

Wirt Atmar