Please refer to the upstream bug at:
https://bugzilla.samba.org/show_bug.cgi?id=5452

Below is a copy of what I wrote in the upstream bug:


Client:
Fedora 9 (preview)
package version samba-client-3.2.0-1.pre3.9.fc9.i386

Server:
Windows XP SP3, Intel Laptop, 32 bit

I use
  smbclient '//192.168.2.51/moz' -U kaie
then
  put hello

"hello" is a file of size "6 bytes", containing "hello".

Actual behavior:
smbclient prints:
  smb: \> put hello
  putting file hello as \hello (0,0 kb/s) (average 0,0 kb/s)
and the destination gets a zero bytes file

Expected behavior:
get the correct file at the destination


I tested with different files, always zero bytes.


Additional info:
Same server, same client commands, same input file, but using a Fedora 8 client
(version 3.0.28a) it works fine!


It's independent of the input file, I always get zero bytes.

I did a network trace with wireshark (thanks to Andrew Bartlet for helping), he
looked at it, and he concluded, it's a good trace for sending a zero byte file.

I did an strace, I see smbclient does a state64, it gets the expected file size
(6 bytes), it successfully opens that file, but never reads from it! It does
something other actions, but then closes the file.

Thanks to Simo Sorce who reproduced this bug with latest samba code.