home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.appletalk:4202 comp.protocols.tcp-ip:5620
- Newsgroups: comp.protocols.appletalk,comp.protocols.tcp-ip
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!caen!uvaarpa!concert!samba!gogan
- From: gogan@hermes.oit.unc.edu (Jim Gogan)
- Subject: NCSA Telnet/MacTCP/Mac LC
- Message-ID: <1992Dec15.193020.4233@samba.oit.unc.edu>
- Originator: gogan@hermes.oit.unc.edu
- Keywords: MacTCP, NCSA Telnet
- Sender: usenet@samba.oit.unc.edu
- Nntp-Posting-Host: hermes.oit.unc.edu
- Organization: University of North Carolina, Chapel Hill
- Date: Tue, 15 Dec 1992 19:30:20 GMT
- Lines: 36
-
-
- We have been experiencing an on-going problem that, now that the semester is winding
- down, we're trying to push to find an answer to. Basically, we have found that it
- is very easy (just by typing real fast, for example) to lock up an LC running telnet
- sessions (doesn't matter to which hosts) with:
- - NCSA Telnet (either version 2.3 or 2.5) AND
- - MacTCP (version 1.1)
- Doesn't matter what brand of Ethernet adapter in the Mac; doesn't matter whether I'm
- running System 6 or 7.
-
- We do NOT have this problem running SU/Mac and MacTCP, nor do we have this problem
- running NCSA ver 2.5 with hardware=ether.
- Has anyone else seen this?
-
- One interesting point that may be relevant. I connected our lil'ol'Lanalyzer,
- filtering for packets to-from the Mac LC I was working on. And noticed the
- following:
- - when using NCSA Telnet with hardware=ether, the TCP Window size used by the Mac
- is whatever I specify with the rwin= parameter in config.tel (no surprise there); I
- used values from 512 to 4096 -- all was OK;
- - when using SU/Mac IP with MacTCP, the TCP Window size used by the Mac is 1336;
- - 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.
-
- Any liklihood that this is related to our problem, and, if so, is there any way to
- change parameters like this for MacTCP (or is it up to the application to deal with
- that)?
-
- Pointers will be - as always - greatly appreciated. Please respond to me directly
- thru e-mail. I'll post the appropriate response (if any).
- Thanks!
-
- -- Jim Gogan (Jim_Gogan@unc.edu)
- OIT Networking Systems
- University of North Carolina at Chapel Hill
-