Dania Ramirez Moya
2020-Oct-15 17:52 UTC
[Samba] samba 3 protocol smb negotiation failed with samba4.12
Hello list: I want to connect client samba 3.6 to server samba 4.12 but i have this problem: smbclient -L 10.0.0.2 -U administrator *protocol negotiation failed : NT_STATUS_INVALID_NETWORK_RESPONSE* I know this is about smb version protocol. I have tried some settings but they didn't work. Any idea? Regards
Jeremy Allison
2020-Oct-15 22:16 UTC
[Samba] samba 3 protocol smb negotiation failed with samba4.12
On Thu, Oct 15, 2020 at 12:52:25PM -0500, Dania Ramirez Moya via samba wrote:> Hello list: > I want to connect client samba 3.6 to server samba 4.12 but i have this > problem: > smbclient -L 10.0.0.2 -U administrator > *protocol negotiation failed : NT_STATUS_INVALID_NETWORK_RESPONSE* > > I know this is about smb version protocol. I have tried some settings but > they didn't work.Samba 4.12 doesn't allow SMB1 out of the box. Look into setting "server min protocol" in the 4.x server smb.conf.
Nick Howitt
2020-Oct-16 07:24 UTC
[Samba] samba 3 protocol smb negotiation failed with samba4.12
On 15/10/2020 23:16, Jeremy Allison via samba wrote:> > On Thu, Oct 15, 2020 at 12:52:25PM -0500, Dania Ramirez Moya via samba wrote: >> Hello list: >> I want to connect client samba 3.6 to server samba 4.12 but i have this >> problem: >> smbclient -L 10.0.0.2 -U administrator >> *protocol negotiation failed : NT_STATUS_INVALID_NETWORK_RESPONSE* >> >> I know this is about smb version protocol. I have tried some settings but >> they didn't work. > > Samba 4.12 doesn't allow SMB1 out of the box. Look into setting > "server min protocol" in the 4.x server smb.conf. >IIRC, Samba 3.6 from some sub-version had "experimental" SMB2 support. You could try enabling that. Again, IIRC, it was enabled by setting "server max protocol = SMB2". It may be a better option rather than lowering the security of Samba 4.12.