"Jonathan M. Backus" wrote:
>
>         Has anybody tried to use the telnet client on the HP e3000 to connect to a
> Cisco router?  I'm working on an A500 (MPE/iX 7.0) and when I telnet to the
> Cisco router I get a series of error/warning messages and then a failure
> (see below - IP address has been removed).

> [1]/TECHGRP/BACKUJ>telnet x.x.x.x
> Telnet Client [A7000000]     (C) Hewlett-Packard Co. 1994
> Trying...
> Connected to x.x.x.x.
> Escape character is '^]'.
> Failed to turn on single echo: 68.
> Failed to turn on single echo: 68.
> IPCSend failed: result = 67.

   [...snip...]

Then Wirt writes:

> This is what I get when I do the same thing, telnetting to our Cisco gateway
> router:
>
> Telnet Client [A5500000]     (C) Hewlett-Packard Co. 1994
> Trying...
> Connected to 192.168.1.10.
> Escape character is '^]'.
>
>
> User Access Verification
> Password:

And Jon notes:

> I see your telnet client is a different version (assuming I'm
> readying it right [A7000000] versus [A5500000]).

My results concur with Jon's with version [A6000000], and that was
trying it by connecting first to the 3000 via native telnet, and also
via a DTC TAC.  I can't try NSVT or direct serial DTC right now.

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).

The MPE telnet client works OK for typical 3000/9000 things, but gets
confused with foreign objects, and much of this has to do with the MPE
telnet server (if you connect to the 3000 via telnet first).  Most of
those warnings are lower-level terminal communication options being
negotiated, and the underlying "terminal layer" varies with the type of
connection (again, serial, NSVT, TAC, Native telnet).

Jeff