search for: nt_status_smb_bad_cluster_dialect

Hello, I am trying to connect and browse the Windows file server and get the following error: # smbclient //ente01.xxxx.local/data Password for [xuser at xxxx.LOCAL]: tree connect failed: NT_STATUS_SMB_BAD_CLUSTER_DIALECT OS: FreeBSD 13.1-STABLE Samba 4.16.10_1 I did not find any similar problem. Could you, please, explain what does it mean? I am not able connect to the directory. Have I any configuration errors? Thank you very much. Regards, lk

On 16/05/2023 08:02, Ludovit Koren via samba wrote: > > > Hello, > > I am trying to connect and browse the Windows file server and get the > following error: > > > # smbclient //ente01.xxxx.local/data > Password for [xuser at xxxx.LOCAL]: > tree connect failed: NT_STATUS_SMB_BAD_CLUSTER_DIALECT > > OS: FreeBSD 13.1-STABLE > Samba 4.16.10_1 > > I did not find any similar problem. Could you, please, explain what does > it mean? I am not able connect to the directory. Have I any > configuration errors? > Not one I have come across before, but the word 'DIALECT...

We have the situation where we are trying to send to a server that has a cluster configuration. When we negotiate, it tells us to talk 3.11. When we actually try to send the file, the share's max protocol is actually only 3.02 and so the Microsoft server sends a NT_STATUS_SMB_BAD_CLUSTER_DIALECT, which means they expect the client to reconnect negotiating only 3.02 as max protocol. Looking through the samba source code, up to 4.9.3, I don't really see any support for this capability. Here's some of Microsoft's documentation: 3.3.5.7 Receiving an SMB2 TREE_CONNECT Request When...