🚀 go-pugleaf

In article <1gln72INN8la@calvin.NYU.EDU>, roy@mchip00.med.nyu.edu (Roy
Smith) wrote:
> 
> gogan@hermes.oit.unc.edu (Jim Gogan) writes: HOWEVER, when using NCSA Telnet
> > with MacTCP, the TCP Window size supposedly used by the Mac (as shown in
> > the packet trace) is 4788; that just seems kinda odd to me.  Of course,
> > the rwin parameter in config.tel has no effect if you're using MacTCP.
> 
> 	I wonder if this is in any way related to the extremely slow
> performance we get with Telnet.  We run NCSA Telnet 2.4 and 2.5 on

And I wonder if this is related to the intermittant problems I
have with Telnet.  Sometimes we have a pair of machines that cannot
talk to one another via telnet; either machine can ping the other
so I *know* they have a working physical connection, and either
machine can operate via telnet with *every other machine* (here or
thousands of miles away) that I try.  The problem seems to be
related to initial protocol negotiation.

What's even stranger is that if I am trying to open a Telnet session
and it's not working, I can open a second ftp session to the same
host.  Not only does the ftp connection work *fine*, but once it
starts the problem with the telnet session suddenly goes away by
magic!?!?

The host involved is a Silicon Graphics workstation running
Irix 4.0.1 System V; the clients are Macs running NCSA Telnet
and MacTCP 1.1  (I know there's a newer version out, but thanks
to Apple's ridiculous new license policies we *cannot* afford it).


Matt Healy
"I pretend to be a network administrator;
 the lab net pretends to work"

matt@wardsgi.med.yale.edu