PVJQC@CUNYVM.BITNET (01/24/91)
I recently upgraded two NeXTs with release 2.0. In all we have three NeXTs
on Netinfo network and the third one is still running 1.0.
I noticed that I could not use NCSA Telnet (ver. 2.2D) running on PS/2 to
connect to these two NeXTs with 2.0. It works fine with the NeXT running
1.0.
NCSA ftp seems to be working fine and so does rlogin and telnet from all the
three NeXTs.
The symptoms are, NCSA telnet does not return login prompt. Alt-Q returns
YES response, Alt-M returns some WILLS and WONTS.
Any clues? Any response will be appreciated.
Thank you.
-------
*********************************************************
* PRASHANT V. JOSHI *
* CITY UNIVERSITY OF NEW YORK. *
* INTERNET ADDRESS: PVJQC@CUNYVM.CUNY.EDU, *
* BITNET ADDRESS : PRASHANT@QCVAX.BITNET *
* *
*********************************************************eps@toaster.SFSU.EDU (Eric P. Scott) (01/27/91)
In article <91024.102510PVJQC@CUNYVM.BITNET> PVJQC@CUNYVM.BITNET writes: >I noticed that I could not use NCSA Telnet (ver. 2.2D) running on PS/2 to >connect to these two NeXTs with 2.0. It works fine with the NeXT running >1.0. 2.2D is a Clarkson University derivative of NCSA Telnet 2.2 for the IBM PC. The two most recent BSD telnetd releases tickle an option negotiation bug in the PC software that has since been fixed. Upgrade to omnigate.clarkson.edu:pub/cutcp/v2.2-D/cutcp.zoo Since NeXT 2.0 supports linemode telnet (yeah!), NCSA's current beta (2.3b14) may be worth trying: zaphod.ncsa.uiuc.edu:NCSA_Telnet/PC.2.3beta/tel23bin.zip (a self-extracting .exe is also available) -=EPS=-