The Samba-Bugzilla – Bug 3967
Problem accessing shares after upgrade to 3.0.23a with smbclient
Last modified: 2006-08-04 12:20:22 UTC
after upgrading my debian Sarge distribution with apt-get to 3.0.23
i have some troubles to access 3 shares on Windows 2000 and 2003 Server.
When trying to access them over smbclient i get the following error messages:
:~# smbclient //ente/Axapta_Dokumente -U Administrator -d 2
added interface ip=192.168.100.121 bcast=192.168.100.255 nmask=255.255.255.0
Domain=[APE-BERLIN] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
smb: \> ls
client_check_incoming_message: received message with mid 9 with no matching send record.
SMB Signature verification failed on incoming packet!
Server packet had invalid SMB signature! listing \*
Error in dskattr: Server packet had invalid SMB signature!
With kerberos authentication i get the same error but different mid number.
My smb.conf lists a server signing = auto
I can not figure out how to attach level 10 logfile and raw tcpdump file, sorry
Created attachment 2066 [details]
tcpdump -s 1024 -vvvnNw tcpdump.raw not port ssh
Created attachment 2067 [details]
smbclient //192.168.100.118/Axapta_Dokumente -d 10 -k -U Administrator -l /root/
Same problem for me, a detailed description with log file is available here :
I think I understand the problem - give me a little while to create a patch.
Created attachment 2074 [details]
Please try this patch. This should fix the secondary trans2 replies signing issue.
If you ok it I'll include it in 3.0.23b.
Created attachment 2075 [details]
Slightly better patch that enters the trans state after the first trans call send - this will work for receiving secondary and subsequent replies. I'm committing this to SAMBA_3_0 and SAMBA_3_0_23. PLEASE TEST !
*** Bug 3968 has been marked as a duplicate of this bug. ***