STATUS_ACCESS_DENIED - cannot connect. Does the SambaLibrary not support Windows Server 2016 default file share? about smblibrary

[TalAloni]

Hi,
Assuming you are entering the right credentials and use the correct authentication parameters, the only thing left is message signing (either SMB signing or NTLM MIC), which SMB2Client does not currently support.
IIRC SMB signing was not required to connect to Windows Server in the past, but perhaps Microsoft changed this in a later update)

[nddipiazza]

Yep that is the answer. https://blogs.technet.microsoft.com/josebda/2010/12/01/the-basics-of-smb-signing-covering-both-smb1-and-smb2/ It is only enabled by default on domain controllers! (which i happen to be doing my testing against)

…

On Sat, Apr 13, 2019, 3:29 PM TalAloni ***@***.***> wrote: Hi, Assuming you are entering the right credentials and use the correct authentication parameters, the only thing left is message signing (either SMB signing or NTLM MIC), which SMB2Client does not currently support. IIRC SMB signing was not required to connect to Windows Server in the past, but perhaps Microsoft changed this in a later update) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACIpOUcp29V39V84Zb0bkK8-GHwCgQg3ks5vgj4RgaJpZM4cuHQD> .

[nddipiazza]

Is it a huge change to add this? I can imagine some of my higher security customers will end up wanting this.
I know you turn out changes like magic on this thing so I figured I'd ask

[TalAloni]

The infrastructure was already in place, so it was only a few lines of code to add SMB signing to the SMB2 client. I've tested it briefly and pushed it to master.

[nddipiazza]

dude... you are amazing!!

[nddipiazza]

Confirmed. Works as expected.