Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!mcnc!gatech!bloom-beacon!mit-eddie!ll-xn!ames!ucbcad!ucbvax!CUNIXC.COLUMBIA.EDU!cck
From: cck@CUNIXC.COLUMBIA.EDU.UUCP
Newsgroups: comp.protocols.appletalk
Subject: Re:  KIP code vs ultrix
Message-ID: <8710311557.AA25472@columbia.edu>
Date: Sat, 31-Oct-87 10:58:15 EST
Article-I.D.: columbia.8710311557.AA25472
Posted: Sat Oct 31 10:58:15 1987
Date-Received: Mon, 2-Nov-87 06:18:07 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 26

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