FSCTL_VALIDATE_NEGOTIATE_INFO with Bad SMB2 signature for message

[Mihail Stefanov]

Hi Jones,
version is, Windows 10 [Version 10.0.10240].
After changing max protocol to SMB2_10 (beside I was using SMB2 which defaults to 2_10), which I tried even before, I got same error.
Some other ideas?

Regards
Mihail
On Sep 13, 2016, at 12:26 PM, Jones Syue <jonessyue at qnap.com<mailto:jonessyue at qnap.com>> wrote:

Hello Mihail,

Could you help check which version of both win10 and ws2012r2?
"WINDOWS+R" > Run > input "winver" would prompt detailed version.

And could you also check "max protocol" in the smb.conf,
assigned with "SMB2_10" and restart samba service, thank you.
The smb.conf supposed to look like:
[global]
max protocol = SMB2_10

--
Regards,
Jones Syue | 薛懷宗
QNAP Systems, Inc.

On Tue, Sep 13, 2016 at 3:54 PM, Mihail Stefanov <mihaillive at hotmail.com<mailto:mihaillive at hotmail.com>> wrote:
Hi,
Using samba-4.3.5, with Windows 10 I got during FSCTL_VALIDATE_NEGOTIATE_INFO responseNT_STATUS_ACCESS_DENIED, because of  "Bad SMB2 signature for message" in smb2_signing_check_pdu.

Using bellow article, I can make it work for Windows Server 2012 r2(like a client), but this flag is not working for Windows 10.
https://blogs.msdn.microsoft.com/openspecification/2012/06/28/smb3-secure-dialect-negotiation/

Is there some solution or fix in latest version of samba or still not implemented, or may be I am doing something wrong?
Why the session_key does not match?

Regards
Mihail