Looking at the trace you provided, if I had to guess this is an issue with SMB signing. My analysis is below:
frame 51 - client after determined in the initial neg protocol exchange that SMB2 is supported, now starts another neg protocol to determine which version of SMB2 can be used. Note the "Security Mode" of 0x02 and that "Signing Require = True but Enabled = False"
frame 53 - controller response and again not the security mode section of the frame "0x03 with both Signing Required and enabled set to True"
In an SMB conversation the last exchange of frames that can occur before SMB signing needs to be confirmed is the "Tree Connect". In your case, the conversation stops at Session Setup, which is not unexpected if SMB Signing is an issue. Start with investigating SMB signing, could start by setting the client to "Required" and re-test.