Xref: utzoo comp.sys.att:11988 comp.protocols.tcp-ip:15276 Path: utzoo!telly!attcan!ram From: ram@attcan.UUCP (Richard Meesters) Newsgroups: comp.sys.att,comp.protocols.tcp-ip Subject: Re: WIN-TCP Problem on 3B2/500 Message-ID: <13907@attcan.UUCP> Date: 14 Mar 91 14:09:35 GMT References: <1991Feb25.214152.27244@prism.poly.edu> <1991Feb27.220337.29559@cbnewsj.att.com> Distribution: na Organization: AT&T Canada Inc., Toronto Lines: 32 In article <1991Feb27.220337.29559@cbnewsj.att.com>, duckie@cbnewsj.att.com (john.c.mc millan) writes: > - TCP under WIN/3Br3.2 seems to be argumentative with > earlier releases: rumor has it that as a result > of fixing a long-term bug regarding window-sizing, > negotiation-arguments occasionally erupt between > 3.2 systems and earlier ones. I've seen 99% of > system CPU disappear for 30 minutes running. > > It's possible the now-available version has > employed some strategy to counter this, but I'd > confirm that, or convert all your 3B2's AND 386's > at one time! We did convert, and we're quite > enthusiastic about the result. > I was wondering if the version you were running was the original version I obtained from the States. But this confirms it. The release version of WIN TCP 3.2 has a switch in /etc/master.d/tcp caled 42COMPAT (or COMPAT42, I can't remember which way around) that defaults to the BSD4.2 window size. If you're going to run a network with 3.2 and 3.01 TCP/IP intermixed, you _have_ to set this and rebuild the system (Defaults to unset 42COMPAT = 0). Regards, ------------------------------------------------------------------------------ Richard A Meesters | Technical Support Specialist | Insert std.logo here AT&T Canada | | "Waste is a terrible thing ATTMAIL: ....attmail!rmeesters | to mind...clean up your act" UUCP: ...att!attcan!ram | ------------------------------------------------------------------------------