I've just had this problem as well and here's what I did:
In smb.conf add the following in the [global] section:
client signing = no
client use spnego = no
I'm backing up an old Windows 2000 box, and without turning off client signing
and spnego I was getting errors on any file or directory t
Neimar writes:
> No it didn't ... I tried to change the charset but I still get the error.
>
> I don't discard the possibility of a charset problem because I have another
> windows station that is being successfully copied, however this second
> station doesn't have any special characters in th
Did Micha's suggestions solve the problem?
Craig
-- Forwarded message --
To: Neimar Volpini <[EMAIL PROTECTED]>
From: Micha Silver <[EMAIL PROTECTED]>
Cc: backuppc-users@lists.sourceforge.net
Date: Fri, 4 Jul 2008 23:13:11 -0700
Subj: Re: [BackupPC-use
lver <[EMAIL PROTECTED]>
Cc: backuppc-users@lists.sourceforge.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 "S
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
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
