custead@sask.UUCP (Der cuss) (10/29/87)
We are using kinetics boxes to reach a variety of ethernet hosts. Whenever we telnet from a mac to an ULTRIX host, the connection hangs after a small number (20 to 50) lines of output. (There is no problem connecting and logging in.) A typical symptom is to issue 'who' or 'ls' and get ONE line of output, including cr-lf, then hang. After about a minute the connection closes, apparently due to a timeout. This problem occurs with both SU-MACIP and NCSA Telnet, so I suspect the problem is in the interaction of the KIP code with Ultrix. The problem does NOT occur when going to a host running UNIX or VMS. We are running the 0987 KIP code, although the 0287 release behaves the same. We are running Ultrix 1.2 and 2.0. The KIP code works fine when using TCP/IP with non-ultrix hosts. And telnet from these hosts to the ultrix hosts also works. So we don't know what might be causing this. Is anyone using KIP and Telnet with ULTRIX? Successfully? Are we missing something? Larry R. Custead Univ of Saskatchewan ihnp4!sask!custead custead@sask.bitnet
meltsner@athena.mit.edu (Ken Meltsner) (10/30/87)
Try setting "-trailers" in the ifconfig qe0 in your /etc/rc.local The default appears to be "trailers" and whenever a long packet gets sent, the Telnet will hang. "-trailers" did it for us. [I have only a vague idea of what a trailer is, anyway, but this solution comes from our local network guru.] --Ken
cck@CUNIXC.COLUMBIA.EDU.UUCP (10/31/87)
We've used all versions of KIP sucessfully with Ultrix 1.0 through Ultrix 2.0-1. Since the KIP model has IP packets on DDP forwarded through the Kinetics box, it is unlikely that it is a problem with the IP in KIP - though it does have some interaction with the outgoing pkt. In any event, given that you made a connection, it sounds far more likely that there is a problem at the TCP or TN level. One problem that affects 4.3 & Ultrix 1.2 & Ultrix 2.0 sites is a problem with the Telnet TCP window. When you see this, output stops for no good reason; however, you can resume it by hitting a return, etc. I forgot the details of why this happens, but if you bring up the Telnet low window close to the Telnet window on the pc/mac, then the problem goes away (hitting the return seems to expand the window). This may or may not be related to the problem you are seeing. We've used NCSA Telnet without problems, but I adjusted the windows to the recommended values (something like 512 all around for AppleTalk). The old MacIP package (in MPW) had to tweaked - I had to adjust the Telnet low and high windows (first saw this problem on the PC version of MacIP - PCIP). Charlie C. Kim User Services Columbia University