Samba 2.2.pre3 and DOS clients /read raw

[Jeremy Allison]

On Wed, Dec 05, 2001 at 07:32:30AM +0100, Ph. Marek wrote:
> >> I have a problem using Samba 2.2.pre3 and DOS clients:
> >> On some files the just don't get valid data.
> >> 
> >> I traced the problem to this facts:
> >> - DOS issues SMBread or SMBreadraw calls (I don't know how it decides which
> >> of these)
> >> - On SMBreadraw Samba gives back a "invalid fid" (sniffed with ethereal)
> >> - this fid seems to be in the SMBopen answer given before - seems to be,
> >> because ethereal won't dissect the last part of SMBopen. But the 16bit
> >> value of the fid is there.
> >> 
> >> It does work with NT4, did work with Samba 2.0.4 (or suchlike, I am not
> >> 100% sure) with same configuration.
> >
> >Can you give me the exact means you use to reproduce this
> >please ?
> Well, I traced a little further.
> 
> Please see attached 2 files:
> - setup.txt: Sniffer dump of session setup. Sorry, only server sent packets
> - don't know why, should have both sides.
> - a samba-logfile at level 10: this is interesting at line 1082, where the
> SMBreadraw gets flagged with an error. The DOS commands were "type
> text.txt" and "pc-spez\view.exe". the type worked, the view.exe says
> "illegal .Exe-file"
> 
> Another data point: if I have "read raw=false" in [global], it works (at
> least with DOS) - but is slow, naturally.

Hmmmm. I'm very puzzled by this. I see the open for fileid 10353 (0x2871),
then an SMBread which works ok, then the SMBreadrw that fails with
exactly the same fileid !

This is very strange.....

Jeremy.