Bizarre limit alert.

[Conrad Minshall]

I don't use ECHO yet, but I debugged much the same symptom on a 
WRITE.  I recall the conclusion was that maximum buffer size includes 
the NB wrapper, but I'd have to revisit the code changed to be sure. 
NT dropping the WRITE had bad consequences of course :(

>I've been testing the SMB Echo message and found a very odd thing.
>
>If I send an echo request message to NT4 SP6 with a payload of 4323 bytes
>NT4 responds just fine.  If the payload is 4324 bytes NT4 does not reply.
>
>Of interest, the payload of 4323 bytes generates one ECHO Request and two
>continuation messages on the (Ethernet) wire.  The ECHO Request and first
>continuation message are 1514 bytes in (total) length.  The last
>continuation message is 1498 bytes...16 bytes less than 1514.  Hmmm...
>
>I like weird stuff like this.
>
>Chris -)-----
>
>PS.  W2K doesn't have the same problem.  I can send an ECHO Request with
>      a payload as big as 16611 bytes.  Curiously, at 16612 bytes and above
>      W2K will reset the connection.  "Connection reset by peer".
>
>--
>Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
>jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
>ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
>OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org

-- 
--
Conrad Minshall h:408-446-2323 rad at acm.org / w:408-974-2749 conrad at apple.com

Sig Humor: This email may or may not be a forgery.  It may or may not have
been modified in transit.  It may or may not represent the opinions of the
alleged author.  There is no such thing as PGP.  Rot13 and DMCA will do ya.