Neimar writes:

  

I'm copying a windows 2003 share and at certain point during the copy I
receive this error:

client_check_incoming_message: received message with mid 8341 with no matching send record.
SMB Signature verification failed on incoming packet!
Server packet had invalid SMB signature! listing \Diversos\Material Antigo - fora de uso\SCI\*
Server packet had invalid SMB signature! listing \Diversos\Material Antigo - fora de uso\Sebrae\*
Server packet had invalid SMB signature! listing \Diversos\Material Antigo - fora de uso\SISTEMACB6\*
Server packet had invalid SMB signature! opening remote file \Diversos\Nomes para sofás  Molon.ods (\Diversos\)
Server packet had invalid SMB signature! listing \Diversos\S\*
Server packet had invalid SMB signature! listing \E\*
Server packet had invalid SMB signature! listing \I\*

[snip]

My BackupPC version is:  3.1.0
My smb version is: 3.0.28a-1.fc7 (on Fedora 7)
    

Did Micha's suggestions solve the problem?

Craig

---------- Forwarded message ----------
To:   Neimar Volpini <neimar AT estobel.com DOT br>
From: Micha Silver <micha AT arava.co DOT il>
Cc:   backuppc-users AT lists.sourceforge DOT net <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 4 Jul 2008 23:13:11 -0700
Subj: Re: [BackupPC-users] SMB Signature verification failed - windows 2003

Last week I posted a question that might be the same problem as you're
having. (Subject was "Samba error after update"). After running a yum
update on my CentOS 64bit server, backups from some windows shares -
using smb - started showing the "invalid SMB signature!" error you
listed beow.  The samba package was among the updates.

THese all were directories with hebrew characters in the directory or
file names.  If your problem is with directories with accented
characters, maybe it's the same bug.

After a week fiddling with the backuppc ClientCharset configuration
setting, and no success, here's what I did to finally solve the problem:

In smb.conf there are two charset options: 'unix charset' and 'display
charset'. THese options are apparently used by  smbclient to convert
encoding from the remote client to the server's local charset. I put in
explcitely:

unix charset = utf8  #matches the encoding used by Windows 2003
display charset = iso-8859-8  #matches the encoding on the BackupPC server
In addition to that change, I also ran another yum update, and again got
an update to samba.

So I'm not 100% sure which of those changes fixed the problem, but now I
see the backups with no funny characters, and no errors in the logs.

Cheers,
Micha