Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!swrinde!news.uh.edu!uuneo.neosoft.com!news.blkbox.COM!news.hal-pc.org!usenet From: jhupp@gensys.com (Jeff Hupp) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Telnetd bug or mis-feature? Date: Sun, 30 Jul 1995 13:29:32 GMT Organization: Gensys Technologies Lines: 28 Message-ID: <3vg1fm$iav@news.hal-pc.org> References: <3vf2br$3di@ector.cs.purdue.edu> Reply-To: jhupp@gensys.com NNTP-Posting-Host: wks1.gensys.com X-Newsreader: Forte Free Agent 1.0.82 dpm@cs.purdue.edu (David Moffett) wrote: :Sometime ago, there was a question about telneting INTO a FreeBSD box :yielding confused results. I didn't pay attention or my site's news :spool splatted because I don't remember seeing an answer. :Symptoms: : :I just installed FreeBSD 2.0.5R from CDROM. Previously I was running :2.0.0R. Problem is true on both O/Ses. The caller is NCSA telnet for :DOS which can be fetched from their ftp site. :I wandered into the telnetd sources (in 2.0.0R) and there is some :discussion of a previous BSD bug in telnetd causing such a problem. :Ditto for the 'bugs' section of the man page. :Could someone enlighten me and perhaps add to the FAQ about this problem? I have experenced the same problem, but ONLY with the NCSA telnet for DOS. No other client has given me the same problem. Suggestion for a windows telnet client? Well, how about comt, it will turn any window 3.1 comm program into a telnet client ~ and does not exhibit the problems that the NCSA telnet for DOS does. Archie knows were it is. Jeff Hupp Binder of Daemons