Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!rphroy!caen!uwm.edu!uwvax!daffy!picard.cs.wisc.edu!sparkie
From: sparkie@picard.cs.wisc.edu (Mark Horn)
Newsgroups: comp.sys.next
Subject: telnet from '386 to NeXT...
Keywords: 386-NCSA, NeXT-Telnet
Message-ID: <1991Jun21.161121.3163@daffy.cs.wisc.edu>
Date: 21 Jun 91 16:11:21 GMT
Sender: news@daffy.cs.wisc.edu (The News)
Reply-To: sparkie@uhura.cs.wisc.edu
Distribution: na
Organization: U of Wisconsin CS Dept
Lines: 37

Hello,

I've been trying to telnet from my IBM PS/2 running DOS3.3 with NCSA TN3270
and the Clarkson Packet Drivers to my '030 NeXT running NS2.0.  I remember a few
months ago that this topic came up, but must have missed the resolution. 

I try telneting to the NeXT and it looks like I've established a connection, but
the login prompt never comes up.  It just sits there.  When I do an Alt-M in 
NCSA to get the diagnostic messages that NCSA gives, I get:
--begin 
Host machine not in configuration file
Domain looking for uhura.cs.wisc.edu

Querying the DOMAIN name server

DOMAIN lookup OK for: uhura.cs.wisc.edu
Trying to open TCP connection to: uhura.cs.wisc.edu

DO Option TERMINAL TYPE (WILL)
DO Option TSPEED (WONT)
DO Option Unknown Option (WONT)
DO Option Unknown Option (WONT)
--end

It looks like the NeXT is giving out two options that NCSA doesn't know about.
The strange thing, is that I don't experience this problem when telneting to
ANY other machine.  I can go to DECstations, HP Bobcats, IBM RT's & IBM 
Mainframes.  It seems to just be the NeXT that I can't talk to.

Has anyone run across a fix to this problem?  How about those unknown options -
anyone know 'em?

Thanks for any help,
- sparkie
--
sparkie@uhura.cs.wisc.edu (Mark Horn)
NeXT Campus Consultant @ U. of Wisconsin, Madison