search for: ntlmsspnegotiate

On 1/11/24 04:06, Programnet via samba wrote: > I just want to make sure that Samba LDAP does not support ntlmsspNegotiate authentication and I will have to switch to > Windows Server? That sounds like an inaccurate conclusion. ntlmssp is not new. If you are looking at the conversation in Wireshark, you could tell us what the packets are actually saying, or you could show us your smb.conf and somebody will point o...

pcap is? on my google drive https://drive.google.com/file/d/1GW-vSGratvQ2dOE-iGVPfj5w72ZBaUUR/view?usp=sharing W dniu 1.11.2024 o?01:48, Douglas Bagnall pisze: > On 1/11/24 04:06, Programnet via samba wrote: >> I just want to make sure that Samba LDAP does not support ntlmsspNegotiate authentication and I will have to switch to >> Windows Server? > That sounds like an inaccurate conclusion. ntlmssp is not new. > > If you are looking at the conversation in Wireshark, you could > tell us what the packets are actually saying, or you could > show us your smb.con...

.../samba/sysvol ??????? read only = No [netlogon] ??????? path = /var/lib/samba/sysvol/wenus.local/scripts ??????? read only = No W dniu 1.11.2024 o?01:48, Douglas Bagnall pisze: > On 1/11/24 04:06, Programnet via samba wrote: >> I just want to make sure that Samba LDAP does not support ntlmsspNegotiate authentication and I will have to switch to >> Windows Server? > That sounds like an inaccurate conclusion. ntlmssp is not new. > > If you are looking at the conversation in Wireshark, you could > tell us what the packets are actually saying, or you could > show us your smb.con...

...gt; > > > I don't really understand what DNS configuration has to do with the > problem where when I log into ldap Again a fair comment, but if the DNS was wrong (which it doesn't appear to be), the DC might have been found. > using: sasl it works but when I > use: ntlmsspNegotiate LDAP drops the connection and the logs contain > the entry: [2024/11/05 14:19:11.121983, 3] > lib/ldb-samba/ldb_wrap.c:340(ldb_wrap_connect) > ldb_wrap open of secrets.ldb > [2024/11/05 14:19:11.122344, 3] > lib/ldb-samba/ldb_wrap.c:340(ldb_wrap_connect) > ldb_wrap open of secre...

...r.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; I don't really understand what DNS configuration has to do with the problem where when I log into ldap using: sasl it works but when I use: ntlmsspNegotiate LDAP drops the connection and the logs contain the entry: [2024/11/05 14:19:11.121983, 3] lib/ldb-samba/ldb_wrap.c:340(ldb_wrap_connect) ldb_wrap open of secrets.ldb [2024/11/05 14:19:11.122344, 3] lib/ldb-samba/ldb_wrap.c:340(ldb_wrap_connect) ldb_wrap open of secrets.ldb [2024/11/05 14:19:11.12...

...l which connects to LDAP to get data. FortiClientEMS version 7.0.x worked with Samba without any problem. Unfortunately newer version 7.2.x no longer works. I noticed while examining Wireshark traffic that version 7.0.x connects using authentication: sasl (3). New version 7.2.x authentication: ntlmsspNegotiate (10) and LDAP terminates the connection. Can I configure Samba to solve my problem? I also tested on Samba version 4.17.x. I checked on Windows Server 2012 and 2022 and this problem does not occur here. Best regards, Tomasz ?widerski

On Sat, 2 Nov 2024 09:46:20 +0100 Programnet via samba <samba at lists.samba.org> wrote: > In attach pcap > > My samba config > [global] > ??????? netbios name = DC1 > ??????? realm = XXXX.LOCAL > ??????? server role = active directory domain controller > ??????? server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, > drepl, winbindd, ntp_signd, kcc,