(Message mtu:15)
Date:    02 Dec 1997 22:58:14 GMT
From:    Marc Slemko <marcs@znep.com>
Newsgroups: comp.dcom.sys.cisco
Subject: Re: Cannot reach sites with MTU<1500
X-Return-Path: dhesi@rahul.net
X-Nojunk-Status: OK   0
Organization: WorldGate Inc.  http://www.worldgate.com/
References: <880958743.6326@news.Colorado.EDU> <65ttqn$37e$1@samba.rahul.net> <65uar9$m94$1@news.ibm.net.il> <65unj9$6dv$1@scanner.
     ***worldgate.com> <g61zzv3n6i.fsf@daedalus.crosslink.net>
Nntp-Posting-Host: valis.worldgate.com
Xref:    samba.rahul.net comp.dcom.sys.cisco:41116

In <g61zzv3n6i.fsf@daedalus.crosslink.net> shields@crosslink.net (Michael Shields) writes:

>In article <65unj9$6dv$1@scanner.worldgate.com>,
>Marc Slemko <marcs@znep.com> wrote:
>> Is NT really that dumb?  It should never attempt to send packets
>> which would end up larger than the MSS you advertise.  If you set
>> a low MTU on your link, you will advertise a low MSS.  That means
>> the server should never ever try sending anything larger
>> than the MSS you advertise.

>Right, but if you have a low MTU on an *intermediate* hop then you
>will see this problem.

Correct.  That does not, however, account for the original (erm...
or someone anyway...) poster's case where increasing the MTU on
the client, ie. one end of the path, fixed the problem.