similar to: Samba as DC member UDP ports used

On 30.10.2015 22:13, Jeremy Allison wrote: > On Fri, Oct 30, 2015 at 11:27:55AM +0100, Stefan Pietsch wrote: >> Dear Samba users and developers, >> >> we had the idea of storing S/MIME certificates in the Samba 4 LDAP. >> In the Windows Active Directory Users and Computers tool I can use the >> "Published Certificates" tab to add a certificate to a user

On 05.11.2015 09:18, Andrew Bartlett wrote: > On Tue, 2015-11-03 at 10:21 +0100, Stefan Pietsch wrote: >> On 30.10.2015 22:13, Jeremy Allison wrote: >>> On Fri, Oct 30, 2015 at 11:27:55AM +0100, Stefan Pietsch wrote: >>>> Dear Samba users and developers, >>>> >>>> we had the idea of storing S/MIME certificates in the Samba 4 >>>>

On Tue, 2015-11-03 at 10:21 +0100, Stefan Pietsch wrote: > On 30.10.2015 22:13, Jeremy Allison wrote: > > On Fri, Oct 30, 2015 at 11:27:55AM +0100, Stefan Pietsch wrote: > > > Dear Samba users and developers, > > > > > > we had the idea of storing S/MIME certificates in the Samba 4 > > > LDAP. > > > In the Windows Active Directory Users and

On Thu, 2018-05-10 at 15:48 +0200, Marco Gaiarin via samba wrote: > Mandi! Andrew Bartlett via samba > In chel di` si favelave... > > Ok, i coma back to an old thread, because vendor finally reply. Thanks! > > Little fast-rewind: i own some Konica-Minolta BizHub multifunction > printers/copiers, and i need to ''bind'' it to my new AD domain. > >

Samba team, I'm having some problems to have a client Windows XP, I believe all systems could have the same issue, using Ldap authentication with Samba. This is a native OpenFiler configuration with a local LDAP server for Samba shares. The problem is that sharing is never authenticated where my suspicious is about sambaSID. Basically I create a test user called "rlvcosta". This

to my knowlidge, konica = xerox. and this works fine imo but im not able to look this up now. i did have xerox connected to my ldapS addc’s. i can check this monday. Greetz, Louis > Op 11 mei 2018 om 04:09 heeft Andrew Bartlett via samba <samba at lists.samba.org> het volgende geschreven: > >> On Thu, 2018-05-10 at 15:48 +0200, Marco Gaiarin via samba wrote: >> Mandi!

I stood up a samba 4 (4.0.9) Active Directory domain controller on a Red Hat Enterprise Linux 6.3 server, configured in accordance with the Samba AD DC HOWTO <https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO> , and tailored to the domain name I want. I'm trying to join a Windows 7 Enterprise Edition client to the domain. Windows responds with "Your computer could not be joined

Mandi! Andrew Bartlett via samba In chel di` si favelave... Ok, i coma back to an old thread, because vendor finally reply. Little fast-rewind: i own some Konica-Minolta BizHub multifunction printers/copiers, and i need to ''bind'' it to my new AD domain. But authentication does not work, seems bacause that printer try to use SASL over plain LDAP (no SSL nor TLS). After

Hi All, I have been using Samba 4.15 on CentOS 6.3 64 bit for last 3 months with no issues but suddenly there i am facing below issues. 1. Windows 7 Pro/Ultimate cannot join the domain, but can telnet all the port. 2. Shared resources on Server 2003 which is added to domain is available some time and some time not. For isolating the issue I have temporary removed the server from Domain the

On Sat, 2020-02-01 at 17:22 +0000, Rowland penny via samba wrote: > On 01/02/2020 16:29, Palle Kuling via samba wrote: > > > > Queried against Samba 4.11.4 (query is for OU=Business but response is > > from OU=Test): > > $ldapsearch -D username at internal.xxx.yy -w password -H > > ldaps://192.168.1.1 -s one -b ou=business,dc=internal,dc=xxx,dc=yy > >

Hello all, I just tried this on our setup and it ist the same there. I get results from other OUs. Using sub instead of one I get the "right" results. Regards Christian Am 01.02.20 um 20:26 schrieb Andrew Bartlett via samba: > On Sat, 2020-02-01 at 17:22 +0000, Rowland penny via samba wrote: >> On 01/02/2020 16:29, Palle Kuling via samba wrote: >>> >>>

Mandi! Rowland Penny via samba In chel di` si favelave... > I think that is what Andrew is trying to tell you, the printer needs to > support SASL over TLS/SSL or it will never work. I don't think there is > anything you can do, but I am surprised that the print doesn't already > support it, after all, it isn't something new ;-) Mi confusion grow. ;-) As stated in my

On 05/03/2020 09:57, Andrea Cucciarre' via samba wrote: > Hello, > > I have a customer that complains that Samba (as DC member) uses UDP > during? AD authentication when clients mount a share. > I have run a test and traced network packet and it seems UDP is used > by the CLDAP (Samba server is 10.50.50.35, AD is 10.50.50.85) > > Is there a way to force Samba to use

I'm trying to test/move some of my LDAP-enabled devices from my actual OpenLDAP server(s) to my new samba AD domain. For now, i'm poking with printers, and i'm testing a Konica-Minolta BizHub C224e. Defining user autentication to external source, i can set (between LDAP, NTLM, NDS, ...) 'Active Directory', and i can/must provide the domain naime. After that, DNS and kerberos

I setup a samba4 pdc and successfully added a Windows 2008 machine to the domain. When I start up the "Active Directory Users and Computers" tool, I get a "Naming information cannot be located because: directory property cannot be found in the cache" error. I'm running a pretty up to date version of samba4. The head commit is: commit

The DC is a Windows AD DC. Could you please clarify why i should change setting in the Windows DC instead of the Samba server, which is the one that does the insecure ldap bind? Regards Andrea Cucciarre' On 11/9/2020 3:13 PM, Rowland penny via samba wrote: > On 09/11/2020 13:28, Andrea Cucciarre' wrote: >> My customer complain that in the AD DC they see the following

Hi Rowland, Sorry to inform that none of thus packages solve my problem. But today, with some Tranquil.it helps, I have some news: - Upgrade from 4.11.14 -> 4.12.9 is OK - Upgrade from 4.12.9 -> 4.13.2 : problem is present with Tranquil.it AND Louis package - Fresh install + member join with 4.13.2 is OK (Centos AND Buster packages) Problem only occur when upgrading member to 4.13.2 with

My customer complain that in the AD DC they see the following insecure communication coming from the Samba server (DC member): "The following client performed a SASL (Negotiate/Kerberos/NTLM/Digest) LDAP bind without requesting signing (integrity verification), or performed a simple bind over a cleartext (non-SSL/TLS-encrypted) LDAP connection." So Samba does an insecure LDAP bind and

Am 09.11.20 um 15:42 schrieb cn--- via samba: > What version of Samba is this and do you have "server schannel = no" set > in its smb.conf? It might also be some thing like this option "client ldap sasl wrapping". So it would really help to see the entire smb.conf Regards Christian > > > Regards > > Christian > > Am 09.11.20 um 15:31 schrieb

On 20/04/2020 17:49, Andrea Cucciarre' via samba wrote: > Does the "password server" setting in the smb.conf achieve it? No, you shouldn't use this, you should allow Samba to choose the best DC to use. > > On 4/20/2020 6:40 PM, Andrea Cucciarre' wrote: >> Hello, >> >> Is there a way to provide a list of DC that Samba should try to join? >> I