Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!sdd.hp.com!samsung!munnari.oz.au!comp.vuw.ac.nz!canterbury!cctr119
From: cctr119@csc.canterbury.ac.nz (Ray Jans, Network Consultant, R.Jans@Canterbury.AC.NZ)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Emulex PK4000 and NCSA Telnet
Message-ID: <1991Feb25.111840.104@csc.canterbury.ac.nz>
Date: 24 Feb 91 22:23:38 GMT
Organization: University of Canterbury, Christchurch, New Zealand
Lines: 64

I am having a problem using NCSA Telnet v2.3beta14 with an Emulex
PK4000 type terminal servers configured for reverse telnet connections.
The problem I have is two fold.

Problem 1:

We have a GA8830 computer for our library database that does not have an
ethernet controller. It has a large number of serial ports. Hence we have
used an emulex terminal server configured for reverse TCP so that PCs running
NCSA Telnet can access the GA. However, Telnet sends a carriage return (CR)
followed by a linefeed (LF) which is interpreted by the GA as two ends of
records. I want to be able to configure NCSA Telnet to send a
carriage return followed by a null instead.
The crmap=4.3BSDCRNUL in config.tel doesn't seem to do it.
The line

  set key \13 13

in the keyboard mapping file doesn't do it either. Do I need to modify the
source code? If so, where is the code that needs to be changed?
I have the source for NCSA Telnet and a Turbo C compiler. Do I need anything
else (eg an assembler) to regenerate the telbin.exe file? Any suggestions
as to which make (command) files I should look at to recompile all source
files and link all object files?

Problem 2:

NCSA Telnet tries to negotiate connection modes with the terminal server
when establishing a connection but the terminal server doesn't
interpret the codes it receives from NCSA Telnet. Instead it sends them
onto the terminal port so that the host connected to the terminal
server echoes back the codes. The host only has RS232 ports and does
not understand anything about TCP/IP or Telnet.
In particular the following codes are echoed back by the host to the
PC:

[Sent: Do Echo]
[Sent: Will Suppress GA]
[Sent: Do Supress GA]
[Recd: Do Echo]
[Sent: Wont Echo]
[Recd: Do Supress GA]
[Recd: Will ??]
[Sent: Dont ??]
[Recd: Wont Echo]
[Recd: Do Suppress GA]
[Recd: Will Suppress GA]
[Recd; Dont Echo]

Does anyone know how to set up
reverse telnet on an emulex server to work properly with NSCA Telnet?
Alternatively, is there a way of turning off the mode negotiation at
connect time in NCSA Telnet?

Thanks in advance

Ray Jans
Network Consultant
Computer Services Centre
University of Canterbury
Christchurch
New Zealand
Email: r.jans@canterbury.ac.nz
fax: CHCH 642-999


Brought to you by Super Global Mega Corp .com