Path: utzoo!attcan!uunet!europa.asd.contel.com!sura.net!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: NeXTStep 2.0 and NCSA Telnet.
Message-ID: <1991Feb1.133403.19495@ni.umd.edu>
Date: 1 Feb 91 13:34:03 GMT
References: <91031.224509PVJQC@CUNYVM.BITNET>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 15
Nntp-Posting-Host: sayshell.umd.edu

>The new telnetd in NextStep 2.0 comes from 4.3-Reno, and seems to be,
>shall we say, too sophisticated for old programs like NCSA Telnet
>(and just about every other telnet in the known universe). To fix the
>problem, you have to replace the new telnetd with the old one from
>1.0. 

It seems to me that the way to "fix" this problem is to fix the problem,
and not the symptom.  Your problem is NCSA telnet, and not the telnet 
daemon on the NeXT.  

Replacing the telnetd on the NeXT makes it possibe to operate with your
NeXT, but you're still going to be stuck if you try to connect to any
other machine that provokes the NCSA telnet bug.

louie