home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!odin!trier
- From: trier@odin.ins.cwru.edu (Stephen C. Trier)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: ip segment size negotiation NEED HELP!
- Date: 5 Sep 1992 03:45:45 GMT
- Organization: Case Western Reserve University, Cleveland, OH (USA)
- Lines: 23
- Message-ID: <189ah9INN4kf@usenet.INS.CWRU.Edu>
- References: <1992Sep4.160201.22932@uswmrg.mrg.uswest.com>
- NNTP-Posting-Host: odin.ins.cwru.edu
-
- In article <1992Sep4.160201.22932@uswmrg.mrg.uswest.com> philc@msmgate.mrg.uswest.com (Phil Corchary) writes:
- >problem: as reported by a sniffer on the line: the segment size coming
- >down from the Tandem is 1500 ... going up from the Mac to the Tandem
- >the segment size is being negotiated down to 590 ...
-
- I just ran into this problem with a VAX running VMS and WIN/TCP. A PC/IP-
- derived FTP couldn't fetch from it, because the VAX wasn't defaulting to a
- 536-byte maximum segment size (MSS) as it should have. When I modified the
- PC TCP to send the TCP MSS option with an MSS of 536, the VAX *still* sent
- 1500-byte packets.
-
- One solution is to reduce the MTU on the Tandem to something smaller, if
- possible. This will reduce throughput when talking to machines capable of
- the maximum MTU, but will provide compatibility with the Mac.
-
- The solution to our problem, though, was to upgrade WIN/TCP to its current
- release. :-)
-
- --
- "Beware of programmers who Stephen Trier
- carry screwdrivers." Network Services Engineering, IRIS/INS/Telecom
- Leonard Brandwein Case Western Reserve University
- trier@ins.cwru.edu
-