Telnet problems

Deborah Jackson deb at gt-cmmsr.UUCP
Wed Feb 5 16:38:13 AEST 1986


We have a very strange problem with our telnet program.  Our Vax 11/780
is running 4.2BSD (BRL) UNIX(TM).  The problem is that it seems to have
its own version of flow control which follows no protocol.  Whenever invoked,
either through our ethernet to our Data General or through the software
loop-back to itself, it stops after a seemingly arbitrary number of 
characters.  Typing any character (except ^S) causes it to continue
it's output.  Those characters are stored up (i.e. type-ahead) and
displayed after it's finished cat'ing a file, etc.  Since any character
will restart it, it's impossible to interupt a program's output -- ^Z
doesn't work either.  (It's a general nuisance.)

Here are the things I know for sure:
 1) It doesn't matter whether the built-in flow control switch is set or not
 2) telnet from the Data General to the Vax works just fine, so I don't 
    think it's a psuedo-port problem or a telnetd problem.
 3) Decreasing BUFSIZ (to force more flushes) helps a little, but doesn't
	solve the problem.
 4) rlogin works just fine (but the DG can't handle it--otherwise I wouldn't
	care if telnet worked or not!)
 5) ftp also runs without a hitch.

I've worked on several Vaxen running 4.2BSD and never seen this problem.
I've also never worked on a Vax with dmf32's before now, which leads me 
to believe they are the culprit.

Has anyone ever seen this problem?  Has anyone run telnet with dmf32's???
Any suggestions are greatly appreciated.

Thanks in advance,
Deb


-- 
Deborah Jackson

School of Electrical Engineering, Georgia Tech, Atlanta, GA 30332
uucp:  ...!{akgua,allegra,hplabs,ihnp4,seismo,ulysses}!gatech!gt-eedsp!deb
                                                                 ^^^^^



More information about the Comp.unix.wizards mailing list