Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!cbosgd!ulysses!ucbvax!NPRDC.ARPA!stanonik
From: stanonik@NPRDC.ARPA.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: xerox -> 4.3bsd telnet
Message-ID: <8702181909.AA15985@pacific.ARPA>
Date: Wed, 18-Feb-87 14:09:00 EST
Article-I.D.: pacific.8702181909.AA15985
Posted: Wed Feb 18 14:09:00 1987
Date-Received: Fri, 20-Feb-87 02:04:10 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: stanonik@nprdc.arpa
Organization: The ARPA Internet
Lines: 26
Approved: tcp-ip@sri-nic.arpa

Hello,

We recently installed a xerox 1186 (dandytiger?) running koto
release 2.0.  Telneting from the 1186 to our vax 780 running
4.3bsd hangs, apparently because the 1186 doesn't respond to
the vax telnet server's "do terminal-type" negotiation.  The
4.3bsd telnet server waits in a loop for the "will/won't terminal-type"
response, processing options, but not starting a login process.
That seems unforgiving (although seemingly legal) from 4.3bsd.
We've hacked a version of the 4.3bsd telnet server, which omits
the terminal-type negotiation, and put it on another port, but
can't convince the 1186 to try the alternate port.  Anyone else
encountered this (the xerox folks say other sites have 1186s
telneting to 4.3bsd machines)?  Any idea how to convince the
1186 to use an alternate port for telnet?  Or, is 4.3bsd wrong
to "hang" waiting for the "will/won't terminal-type" response?

Thanks,

Ron Stanonik
stanonik@nprdc.arpa

ps.  The 1186 also seems to violate the rfcs by sending the
"terminal-type is" subnegotiation without first receiving
a "terminal send".  Or maybe it thinks that is a suitable
response to "do terminal-type"?