Bug 4028 - no message popup for message with smbclient -M
no message popup for message with smbclient -M
Product: Samba 3.0
Classification: Unclassified
Component: smbclient
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2006-08-17 08:14 UTC by Dieter Ferdinand
Modified: 2007-09-15 02:24 UTC (History)
1 user (show)

See Also:

Test-File (126 bytes, text/plain)
2006-08-18 02:43 UTC, Dieter Ferdinand
no flags Details
r25169 (412 bytes, patch)
2007-09-14 13:35 UTC, Volker Lendecke
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Ferdinand 2006-08-17 08:14:35 UTC
i have a problem with smbclient -M and a message with this format:

the message have 2 lines and 126 characters. this messages is saves in a file for testing. i test it with lines with different lenght, but this makes no change.
if i send this message with smbclient -M host<messagefile, i get no message popup at the host.
i use ethereal to log transfer and found the packets, which smbclient is sending with the message.

a message with same character count and 3 lines make no problems or one character more or less works also. only with 2 lines and 126 characters (count with wc) is not displayed.

i change some characters or all, but this have no effect.

i send this message to a host with winxp and win2000, but none of them display the message or log it to systemlog.

i don't know, if this is a problem from windows or samba, but it is not good!

Comment 1 Volker Lendecke 2006-08-17 08:41:20 UTC
Tried it with a cut&paste from the bug report, works for me.

Please re-open with more info like the file that fails for you as an attachement and a sniff of the failed attempt.

Comment 2 Dieter Ferdinand 2006-08-18 02:43:03 UTC
Created attachment 2097 [details]
Comment 3 Dieter Ferdinand 2006-08-18 02:47:45 UTC
you know, that with copy and past more then 126 characters are copied while there are some spaces at the end of the first line ?

to reproduce this error, you must create a text-file (like the test-file) which have a size of 126 bytes and 2 lines with text.

Comment 4 Volker Lendecke 2006-08-18 03:05:50 UTC
Ok, got it reproduced. The trick is to use it against XP and not NT4. NT4 can cope with that 2-liner you sent. Weird one.

Comment 5 Dieter Ferdinand 2006-08-18 04:26:08 UTC
i can it only test with xp and win2000 because i have no running nt4 at the moment.

and with both it don't work with this message and i don't know why.

Comment 6 Volker Lendecke 2006-08-18 04:33:15 UTC
Understood. I just wanted to ack that I could reproduce it. The problem is that right now I'm busy with other stuff.

Comment 7 Frank Lemke 2007-09-11 05:02:54 UTC
I've found out, that the problem is reproducable with messages sent from 'smbclient -M' to Windows 2k or XP with a transfer length of multiples of 127 bytes and multiples of 127 bytes plus 1 byte. That means for example messages with length of 127, 128, 254, 255 etc. bytes are not displayed under Windows!

Comment 8 Volker Lendecke 2007-09-14 13:35:58 UTC
Created attachment 2924 [details]

I've checked in the attached patch as r25169, it fixes the bug for me.
Comment 9 Volker Lendecke 2007-09-14 13:36:49 UTC
The patch fixes it for me, please re-open if it doesn't for you.