similar to: Extend schema on CentOS directory server

Hello, I am trying to deploy an additional read-only replica (aka. 'consumer') in a single-master dirsrv environment. The master, and the other pre-existing consumer servers, are all 'fedora-ds' running on Fedora 7. I'm trying to add a consumer running on Centos 5.5. Ultimately, I intend to replace the Fedora ds servers with Centos dirsrv servers. I'm trying to deploy

I'm running fedora directory server on some boxes in a multi-master arrangement. The problem is that when dirsrv is lauched from init (on boot) the maximum number of allowed file descriptors (ulimit -n) is only 4096. That means that the slapd process can only accept ~4k connections, and it needs to accept ~10k or so. The value for nofile for all users in /etc/security/limits.conf (and

> - ace -d install ovirt has one error : package ovirt-node-image-pxe > not > found I get an error when FreeIPA is set up. Then a whole heap of notices and warning about a missing dependancy (presumably FreeIPA) debug: //freeipa::bundled/Single_exec[ipa_server_install]: Executing '/usr/sbin/ipa-server-install -r ovirt.priv -p 'supersecretpw' -P 'supersecretpw' -a

I am running CentOS DS server (version 8.1.0) in a mixed master setup. I am looking for the best way to extend the schema without breaking replication? I was successfully able to extend the schema on my two servers manually but replication broke after a restart of dirsrv. [03/Dec/2012:11:04:17 -0400] NSMMReplicationPlugin - agmt="cn=web-ldap02" (web-ldap02:389): Unable to acquire

Hi all, I want to extend the samba schema for freeradius, they unfortunately do not provide the schema in ldif format anymore. Do you know if samba does accept OpenLDAP formatted schema or if I have to convert it? Best regards -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital

192.168.127.129 is the core DNS server. It forwards anything in the windows subdomain straight to the DCs, so it doesn't matter if this client is pointed at the DC or the main DNS server. Either way, it still does the wrong behavior, which is use the short .WINDOWS instead of . WINDOWS.CORP.XXX.COM I removed all .tdb files, purged /var/cache/samba, removed /etc/krb5.tdb, and deleted the

I can share my notes, we authenticate UniFi clients via Freeradius against Samba AD. We also check group membership which you might or might not need: ## 4 FreeRADIUS ### 4.1 Basics ```bash apt install freeradius freeradius-ldap freeradius-utils # create new DH-params openssl dhparam -out /etc/freeradius/3.0/certs/dh 2048 ``` ### 4.2 Configure Authentication - modify mschap to use winbind,

jonathan.fisher at freeradius:~$ sudo net ads join -Uadministrator Enter administrator's password: Using short domain name -- WINDOWS Joined 'FREERADIUS' to dns domain 'windows.corp.XXX.com' jonathan.fisher at freeradius:~$ hostname freeradius jonathan.fisher at freeradius:~$ hostname -d windows.corp.XXX.com jonathan.fisher at freeradius:~$ hostname -f

Hello Alexander, thanks Alexander for these configuration snippets. Which version of Samba are you using? Is this on debian bullseye? Is the FreeRADIUS server installed on a DC or on a Domain Member? (I just tested the latter). is "ntlm auth = yes" OK for the DCs and the domain member or does it have to be "mschapv2-and-ntlmv2-only" for all servers (DCs + Member)? It

Hey Rowland, be kind and avoid passive aggressive comments. I'm just looking to try and get this to work, thanks. If I knew everything already, I wouldn't be here asking questions and trying to solve my own problem. I appreciate your help so far, but if you don't have anything nice say, please just ignore this thread. So: jonathan.fisher at freeradius:~$ sudo hostname -y hostname:

It seems to me that the ver of FreeRadius is 1.0.1: yum list | grep "radius" freeradius.i386 1.0.1-3.RHEL4 installed freeradius-mysql.i386 1.0.1-3.RHEL4 base freeradius-postgresql.i386 1.0.1-3.RHEL4 base freeradius-unixODBC.i386 1.0.1-3.RHEL4 base According to freeradius.org, this

Here's a random question... would it matter if our domain has trust relationships setup? *Jonathan S. Fisher* *VP - Information Technology* *Spring Venture Group* On Wed, Dec 9, 2015 at 9:34 AM, mathias dufresne <infractory at gmail.com> wrote: > Hi Jonathan, > > You wrote: > domain windows.corp.springventuregroup.com > search windows.corp.*pringventuregroupcom* >

Hi, I was able to join the domain correctly and from what I Understand I should see it added as A computer on my Windows 2008 Server PC. Is this true? But when I do a wbinfo -u I do not see my domain users listed. I was wondering if this is because we installed winbind4 rather than winbind? I installed samba4 and winbind4 in Ubuntu 11.04 LTS Thanks for everyones help, Scott root at

Hi Matthias, we?re using Debian Bullseye with the backports repo. So version is a mixture of - Samba version 4.17.3-Debian - Samba version 4.17.7-Debian We?ve installed it directly on the DC?s as well. In my opinion using "ntlm auth = yes? should be fine. Did you try using a simple RADIUS secret? In my experience long secrets or ones containing special characters don?t work very well. I

Hi Alexander, I'm terribly sorry. We didnt have the "ntlm auth" parameter configured on the DCs at all. I added it and it just works. Thanks for your help. Now I just need to figure out how I can make WLAN-specific LDAP-Group authentication. e. g. production WLAN needs LDAP group "wlan_production" and management WLAN needs the "wlan_management" group. I

It is an issue that I myself would also like to solve. I found multiple threads in samba and freeradius mailing lists. It seems that every couple of months there is question like this either here on FR mailing list and all point down to the same issue, that is: freeradius uses ntlm_auth (even when using winbind with newer freeradius versions, it also in the end uses ntlm_auth). And since

Ok, I finally could try it out, and it seems to actually work, but You need samba 4.7 on all machines, not only AD, but also server with freeradius. I didn't get a chance to test it locally, that is samba AD + freeradius on the same server. Setup: 4.7.6 AD server and 4.6.2 samba member + freeradius didn't work (got simple "nt_status_wrong_password") but: 4.7.6 AD and 4.7.1

All, I'm running CentOS 5.4 and I've installed the CentOS Directory Server by running yum -y install centos-ds* without any errors. But as soon as I attempt to run the setup I get the following: [root at jpdsys3 ~]# /usr/sbin/setup-ds-admin.pl Can't locate Setup.pm in @INC (@INC contains: /usr/lib64/dirsrv/perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi

Bonjour, It seems that freeradius 3.0.1-6.el7 of centOS 7 don't work. When doing very simple authentification (PAP control of ssh login on a switch), I get a segmentation fault when the first accounting packet arrives on the server. Does anyone test succesfully this version of freeradius ? Thanks PS: no error with the compilation of the last source version of freeradius (3.0.7) --

Greetings list, I'm haveing problem with FreeRADIUS v1.0.1-3 which came with CentOS 4.1 FreeRADIUS refuses to use system accounts for authentication. The latest freeradius-1.0.4 is working correctly. Can we have this update or have to wail till RH release new rpm src? Thanks, -j