samba - Jan 2004 - signing failures during smbclient tar operation: SMB signature check failed

(Samba 3.0.1, RedHat 9, share is a w2k3, security = ADS)

Here is a snippet of debug level 3 output of an smbclient tar operation,
with error at the end.  Command is:

# smbclient \\\\snapper\\dfs <password> -U Administrator -E -W CISWINNET
-D home -d3 -Tqca /tmp/test.tar

[2004/01/14 15:05:10, 3] lib/util.c:dos_clean_name(549)
  dos_clean_name
[\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip]
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(673)
  file
\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip
attrib 0x80
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(686)
  getting file
\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip
of size 15593375 bytes as a tar file backup20010502.zipnread=0
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693)
  nread=65520
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693)
  nread=131040
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693)
  nread=196560
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693)
  nread=262080

[snip]

[2004/01/14 15:05:12, 3] client/clitar.c:do_atar(693)
  nread=11597040
[2004/01/14 15:05:12, 1] libsmb/smb_signing.c:signing_good(205)
  signing_good: SMB signature check failed on seq 7!
[2004/01/14 15:05:12, 0] libsmb/clientgen.c:cli_receive_smb(121)
  SMB Signature verification failed on incoming packet!
[2004/01/14 15:05:12, 0] client/clitar.c:do_atar(698)
  Error reading file
\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip
: Server packet had invalid SMB signature!
[2004/01/14 15:05:12, 0] client/clitar.c:do_atar(733)
  Didn't get entire file. size=15593375, nread=11597040
[2004/01/14 15:05:12, 3] client/clitar.c:do_atar(770)
  (7059.76 kb/s) (average 4832.78 kb/s)

This is a 15M file, and it's failing about 11.5M into it.  What 


-- 

Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama - Birmingham
fran@cis.uab.edu
(205) 934-0653

[next time I won't hit send before finishing my thought, sorry]

The interesting thing is that:

# smbclient \\\\snapper\\dfs <password> -U Administrator -E -W CISWINNET
-D home -d3 -Tqca /tmp/test.tar

produces....

\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip
of size 15593375 bytes as a tar file backup20010502.zipnread=0
[2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693)
  nread=65520

[snip]

[2004/01/14 15:05:12, 3] client/clitar.c:do_atar(693)
  nread=11597040
[2004/01/14 15:05:12, 1] libsmb/smb_signing.c:signing_good(205)
  signing_good: SMB signature check failed on seq 7!
[2004/01/14 15:05:12, 0] libsmb/clientgen.c:cli_receive_smb(121)
  SMB Signature verification failed on incoming packet!
[2004/01/14 15:05:12, 0] client/clitar.c:do_atar(698)
  Error reading file
\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip
: Server packet had invalid SMB signature!

whereas....

# smbclient \\\\snapper\\dfs <password> -U Administrator -E -W CISWINNET
-D home\\faculty\\bryant\\bryantback-brblt\\Images\\backups -d3 -Tqca
/tmp/test.tar

works fine.  So it's not the particular file that causes it to fail, but
perhaps when it hits a certain threshold for total amount of data?

Should I be taking this to one of the more technical lists?

Thanks,
Fran