Thread View: comp.protocols.appletalk
2 messages
2 total messages
Started by Sam Wilson
Tue, 26 Jan 1993 12:42
MacTCP and window size
Author: Sam Wilson
Date: Tue, 26 Jan 1993 12:42
Date: Tue, 26 Jan 1993 12:42
48 lines
2572 bytes
2572 bytes
This may be an FAQ (though I've looked in the MacTCP information produced by Eric Behr at spider.math.ilstu.edu but can't find anything relevant) and if so I apologise. We have a number of Macs running various versions of NCSA Telnet (with and without MacTCP), Eudora etc.. We have one particular one, a IIfx with an Apple ethernet card, which occasionally fails to make IP connections to other hosts; not all the time, just sometimes. It is using MacTCP and the problem occurs with both Telnet and Eudora. For the interested what actually happens is that the host accepts the TCP connection and then resets it. The sequence is as follows: 1) Mac sends initial TCP connect packet (SYN) offering window of 1218 bytes and TCP option of MSS of 536. 2) Host responds (ACK and SYN) with its own window size of 4096 and MSS of 1480. 3) Mac then ACKs this packet with its window still set at 1218 and no further TCP options. 4) Host sends RST flag to reset the call. I presume the host has decided that it can't cope with the combination of a TCP window size of 1218 and an MSS of 1480. We get exactly the same behaviour when using either NCSA Telnet or Eudora. On other occasions, i.e. when the thing works, the same Mac advertises a window of 4221, as do other Macs using MacTCP, and everything works beautifully. Since this seems to be independent of the specific application I assume it's a MacTCP problem, possibly a shortage of memory. Unfortunately I don't know of any way of configuring memory for MacTCP (presumably it uses the System heap) and can only guess that there's a general shortage of System memory at the moments when this problem happens. I'll continue to investigate (though the machine is actually 2 miles away from my office!) but if anyone has come across this sort of behaviour I'd be interested in knowing. As I said it's a IIfx and Inter*Poll says System B1-7.0.1, Finder B2-7.0, LaserWriter 7.1.1, Responder 201, AppleTalk 56, AppleShare 7.0. I don't know which version of MacTCP. Sam Wilson Network Services Division Computing Services, The University of Edinburgh Edinburgh, Scotland, UK
Re: MacTCP and window size
Author: John Veizades
Date: Tue, 26 Jan 1993 15:47
Date: Tue, 26 Jan 1993 15:47
24 lines
1830 bytes
1830 bytes
In article <30794@castle.ed.ac.uk>, ercm20@festival.ed.ac.uk (Sam Wilson) wrote: > > Since this seems to be independent of the specific application I assume > it's a MacTCP problem, possibly a shortage of memory. Unfortunately I > don't know of any way of configuring memory for MacTCP (presumably it > uses the System heap) and can only guess that there's a general shortage > of System memory at the moments when this problem happens. I'll > continue to investigate (though the machine is actually 2 miles away > from my office!) but if anyone has come across this sort of behaviour > I'd be interested in knowing. > MacTCP has little to do with the size of window that is advertised to the remote host. The application that is using MacTCP gves MacTCP the memory needed to maintain the connection. The application program needs to give MacTCP sufficient memory to maintain the connection. Application programers should use the formula provided in the MacTCP Programmer's Guide to guide them with memory allocation remembering that their software may be used on links that have a larger datagram size than Ethernet. Programmers should factor the data link MTU in their memory calculations. John Veizades... MacTCP Lead Engineer Apple Computer, Inc.
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads