[Samba] Time capsule and "bad smb"

[James Peach]

2009/2/16 Jeremy Allison <jra at samba.org>:
> On Mon, Feb 16, 2009 at 05:01:53PM +0100, Pietro Battiston wrote:
>> Some update to the mail below: if I understand correctly, there are two
>> different problems showing up:
>> 1) mount.cifs and the Time Capsule (I have no idea on which front the
>> problem is) don't seem to be able to handshake correctly if the share
>> name contains whitespaces. I didn't notice at first glance, but then found
>> some "no such share" errors in dmesg - not reported as output of the
>> command. Then I tried to change the share name (on the Time Capsule,
>> obviously) to a single word and reconnect, and it worked (almost, keep
>> reading).
>> 2) on some particular smb commands - please bear with me if what I say
>> is somewhat imprecise - the Time Capsule sends back packets badly
>> formatted (or that mount.cifs thinks are badly formatted). This happens,
>> in particular:
>> - for some packets that report an error, such as the "no such share"
>> - for some packets during the unmount
>>
>> This is the reason why - as far as I can conjecture - though the
>> handshaking failed because the name of the share could not be resolved,
>> I didn't get a message about that: in the communication where the Time
>> Capsule said "hey, I don't have that share!", some packet was reported
>> as incorrect and dropped.
>>
>> Notice that now it does mount immediately, but when I unmount it takes
>> almost a minute, and in dmesg I get:
>>
>> [341279.777815] Bad SMB: : dump of 48 bytes of data at 0xcc482e00
>> [341279.777836]  00000027 424d53ff 00000074 00018800 ' . . . � S M B
>> t . . . . . . .
>> [341279.777855]  00000000 00000000 00000000
>> 21180000 . . . . . . . . . . . . . . . !
>> [341279.777873]  00960000 0000ff03 0f000000 6401a8c0 . . . . .
>> � . . . . . . � � . d
>>
>> Googling, I found a very similar problem:
>> https://bugzilla.redhat.com/show_bug.cgi?id=191112
>> , in which case it was said to the reporter "the server is buggy, go
>> tell to the producer". Now, before trying, probably in vain, to talk
>> with some Apple guy, I'd like to know the opinion of someone slightly
>> more expert than me (I have used smb/cifs 5-6 times in all my life),
>> also because my "conjecture" doesn't explain everything... in
>> particular it's a mistery for me the fact that one of the two sites I
>> linked in the former email claimed to have mounted successfully a Time
>> Capsule with a share name containing whitespaces. I'll try to contact
>> the writer of that page (notice that before trying changing the share name, I had
>> tried changing the Time Capsule firmware, installing all the 3 available
>> versions with no luck, so the difference isn't there).
>>
>> In the meanwhile, any hint? I anyone connecting to a Time Capsule without
>> problems?
>
> We have an Apple Samba Team member, James Peach. James, any ideas
> on what is going wrong here ?

Volker's suggestion is the best.

Pietro should to <http://developer.apple.com/bugreporter/> and log a
bug against the TIme Capsule. It would be best to attach a packet
trace to the bug. Follow the instructions here:

<http://wiki.samba.org/index.php/Capture_Packets>

I'll try and dig up a time capsule to bring to Connectathon next week
if any of the Linux smbfs folks would like to test against it ...

-- 
James Peach | jorgar at gmail.com