Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.

E1245: Ggate/Telnet failed if client refused TT negotiation

Product: Ggate/Telnet
Platform: All
Status: Fixed for 6.6, fix available for 6.5
Last updated: 2012-02-28 15:45:19

Due to extended functionality in Ggate/Telnet that allows Telnet clients
to use the Telnet terminal type response to specify a CONAME/RESOURCE
for the GCOS connection, the Ggate Telnet server was dependent on the
client negotiating Telnet terminal type. This is not a problem for a
terminal emulator, which normally always uses the Telnet terminal type
response to inform the host which terminal type it is emulating.

Some script languages and applications that are not emulating a terminal
use Telnet to communicate with a host application. These do not
necessarily implement/configure Telnet terminal type negotiation. These
scripts and applications failed with Ggate/Telnet.

The Ggate Telnet server has been modified to default these clients to a
new Host Links terminal type, NVT (Network Virtual Terminal), which is
the absolute minimum client functionality required to use a Telnet
connection. Telnet clients that do negotiate terminal type, but use
VTxxx as the response are also mapped to NVT. The NVT terminal type maps
to a DSA terminal code of 0x2001 so that GCOS sees it as a TTY33. This
is exactly the same strategy as used by the MainWay Telnet server.

NVT can be used explicitly as a Telnet terminal type response for
simple applications/scripts/emulators that have no real terminal
functionality, just simple message exchange with the host application.
NVT can be used generally as a terminal type in Host links, it is not
restricted to Telnet.

For failing Telnet scripts/applications there is no work-around other
than configuring terminal type negotiation if it is available in the
Telnet client.
(c) Copyright 1982-2019 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors