Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!vd09+
From: vd09+@andrew.cmu.edu (Vincent M. Del Vecchio)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: problem with NCSA telnet and NeXT with release 2.0
Message-ID: <wbboXcO00UgKA5nUo3@andrew.cmu.edu>
Date: 24 Jan 91 20:51:52 GMT
References: <91024.103454PVJQC@CUNYVM.BITNET>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 13
In-Reply-To: <91024.103454PVJQC@CUNYVM.BITNET>

I am not sure what the problem is, but we have it also... not with NCSA
telnet, but with a locally modified version of telnet which we use on
most of our Unix machines.  The vendor supplied telnets seem to work.  I
have tried both replacing telnetd on the NeXT with the latest version
from Berkeley (which did not work) and using the latest version of
Berkeley's telnet instead of the locally modified one on the other
machine (which did work, but didn't explain the problem).  If you find
out what the problem is or a work-around, I would like to know about it
too.

-Vincent Del Vecchio
vd09@andrew.cmu.edu
#include "stdsig.h"