[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 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
