[Samba] Workstation Limited to NT1 Protocol

[lingpanda101 at gmail.com]

On 4/19/2016 3:41 PM, Bill Baird wrote:
> I tried disabling SMB1 and enabling SMB2/3 and after reboot, I can't 
> connect to any of my Samba servers...so looks to definitely be a 
> workstation issue.
>
> On Tue, Apr 19, 2016 at 3:32 PM, Bill Baird <bill.baird at phoenixmi.com 
> <mailto:bill.baird at phoenixmi.com>> wrote:
>
>     Just saw that, as well.
>
>     After running the commands to enable SMB2 & SMB3 and
>     rebooting...no luck. Will keep searching for other registry settings.
>
>     On Tue, Apr 19, 2016 at 3:27 PM, lingpanda101 at gmail.com
>     <mailto:lingpanda101 at gmail.com> <lingpanda101 at gmail.com
>     <mailto:lingpanda101 at gmail.com>> wrote:
>
>         On 4/19/2016 3:24 PM, Bill Baird wrote:
>>         When I search for "smb2", I get nothing in my log file for
>>         the NT1 limited system. If it is a workstation issue, that
>>         would be great. I'll search around for what settings to
>>         change. Maybe SMB2 was inadvertently disabled.
>>
>>         Thanks for all of your help on this!
>>
>>         On Tue, Apr 19, 2016 at 3:20 PM, lingpanda101 at gmail.com
>>         <mailto:lingpanda101 at gmail.com> <lingpanda101 at gmail.com
>>         <mailto:lingpanda101 at gmail.com>> wrote:
>>
>>             On 4/19/2016 3:11 PM, Bill Baird wrote:
>>
>>                 [2016/04/19 15:04:46.352217, 10, pid=21600,
>>                 effective(0, 0), real(0, 0)]
>>                 ../source3/smbd/smb2_server.c:3068(smbd_smb2_first_negprot)
>>                   smbd_smb2_first_negprot: packet length 102
>>
>>             Everything looks OK on your MS. Since it's only one
>>             workstation I'm certain it's the issue. You want to look
>>             for this line in your logs. This is what you posted from
>>             your SMB2 connection.
>>
>>             [2016/04/19 15:04:46.352217, 10, pid=21600, effective(0,
>>             0), real(0, 0)]
>>             ../source3/smbd/smb2_server.c:3068(smbd_smb2_first_negprot)
>>               smbd_smb2_first_negprot: packet length 102
>>
>>             Specifically this 'smbd_smb2_first_negprot'. The
>>             workstation should attempt SMB2 and fall back if it
>>             can't. Do you even see this process?
>>
>>             You can also force SMB2 in the registry of the windows
>>             workstation if need be. I wouldn't advise it but it can
>>             be done.
>>
>>
>>
>>
>>             -- 
>>             -James
>>
>>
>>
>>
>>         -- 
>>         *Bill Baird*
>>         Chief Technology Officer
>>         Office: 845-876-8228 x311 <tel:845-876-8228%20x311>
>>         Mobile: 203-545-0437 <tel:203-545-0437>
>>         www.phoenixmi.com <http://www.phoenixmi.com/>
>>
>         Look here if you want to force SMB2 on the windows side.
>
>         https://support.microsoft.com/en-us/kb/2696547
>
>         -- 
>         -James
>
>
>
>
>     -- 
>     *Bill Baird*
>     Chief Technology Officer
>     Office: 845-876-8228 x311 <tel:845-876-8228%20x311>
>     Mobile: 203-545-0437 <tel:203-545-0437>
>     www.phoenixmi.com <http://www.phoenixmi.com/>
>
>
>
>
> -- 
> *Bill Baird*
> Chief Technology Officer
> Office: 845-876-8228 x311
> Mobile: 203-545-0437
> www.phoenixmi.com <http://www.phoenixmi.com/>
>
Can you use Wireshark to see the negotiation phase from the windows 
workstation? Maybe a re-image of the Windows workstation if it's not 
mission critical?

-- 
-James