similar to: ldap search with DN which contains space

Hello guys: I need to know a strategy to identify which dns-backend are Samba4 DC using: BIND9 or Internal? Some time ago someone told me I can check this by verifying if exists the user 'dns-hostname'. But, what if this user has been deleted? Or, what's the situation if I need to get the dns-backend on a replication environment? On the other hand, How can I know if my server is

Hi @ll: I need to get the objectClass of some objects by giving theirs DistinguishedNames. I've try with this: #ldbsearch -H 127.0.0.1 dn='CN=nameTest,CN=Users,DC=example,DC=com' But: # returned 3 records # 0 entries # 3 referrals Any idea? How Can I to specify a DN in ldbsearch command. Thanks. ___________________________________________ Felipe_ González_Santiago The

Hello, I'm installing Samba4 AD from repo Ubuntu16.04. These are the steps I've applied: 1. editing fstab in EXT3 2. install dependencies ( acl attr quota fam libnet-ldap-perl ) 3. install krb5-user, bind9, ntp, winbind, ldbtools and samba. 4. remove smb.conf, if exists 5. samba-tool provision 6. Restart services bind9, ntp and samba 7. config Bind9

When I run a ldbsearch command looking for an object, I get to attributes with the same values: 'dn' and 'distinguishedName'. Then, Is there any difference between them? If not, Why 'ldbsearch' returns this two attributes? _________________________________________ Ing. Felipe_ González_Santiago Universidad de las Ciencias Informáticas Centro de Software Libre The

I guess your DC take the time from an external ntps server. But I want to serve time from the same DC, so this is my ntp config: #nano /etc/ntp.conf server 127.127.1.0 fudge 127.127.1.0 stratum 12 ntpsigndsocket /var/lib/samba/ntp_signd/restrict default mssntp ___________________________________________ Felipe_ González_Santiago KNOW THAT EVERYTHING WILL HAPPEN AT JUST THE RIGHT TIME,

I provisioned a server with Samba4.3 from repo ubuntu16.04. I tested some things, but I can NOT connect to my Samba DC from the Windows DNS client. ADUC, AD Sites and services, and AD Domain & Trusts, connects Ok. But DNS [" Acces is Denied "] does not connect to the Samba4 DC. Any idea? What happens? _________________________________________ Ing. Felipe_ González_Santiago

Hi samba team ! I have found a very strange bug when changing my user's primaryGroupID with ldif files. The bug is very easy to reproduce : 1) Create a user, create a group, add the user to the group ------------------------------- ~# samba-tool user add stduser User 'stduser' created successfully ~# samba-tool group add stdgroup Added group stdgroup ~# samba-tool group addmembers

| My DC is a samba4.3 over Ubuntu 16.04. | I've configured ntp in the same server. | However > when I join a windows 10 client to my domain, this one doesn't | update its datetime. | Once I logging in, I am able to set any datetime. | And more > No matter the windows 10 client' s datetime, I can logging in with | any user of the Active Directory. | I need a proper time sync in

1. I need to know by using a command -if possible- or antoher way, which NIC is samba AD using? Apart of looking for the 'interfaces' option in the smb.conf. So, Exists other way to know that? Because if I coding this method expecting for the smb.conf, I could have problems if smb.conf has been deleted. 2. If during provisioning a DC I don't specify the network interface Samba select

On Mon, 2017-10-16 at 13:07 +0000, Andrej Gessel via samba wrote: > Hello list, > > maybe I saw the same error with backlinks. I try to use Samba 4.7.0 as rodc and perform join with "domain-critical-only"-option. Smb.conf is generated by samba. After starting joined samba I got error like this: Does it change if you don't use that option? > Failed to apply records:

Hello, I have a small test network with a Win2k8R2 DC. I've added a samba4 as second DC in this network. The join seems to run smoothly. But, after the join, this command: ldapsearch -LLL -x -H ldapi://%2Fvar%2Flib%2Fsamba%2Fprivate%2Fldap_priv%2Fldapi -b "dc=test,dc=dom" "(SAMAccountName=Administrateur)" returns some strange results: ? some attributes like unicodePwd

I'm quite confused by this one, as I can't see how this would happen.. but after upgrading my DCs from 4.11.10 to 4.18.5, LDAP searches don't seem to work if they use the :1.2.840.113556.1.4.1941: modifier, aka LDAP_MATCHING_RULE_IN_CHAIN. (Yes, it was a fairly big version jump.. Yes, I should have upgraded much earlier.. Yes, I know 4.19.x is out now as well) Here's a search that

On 6/19/2017 7:51 AM, Viktor Trojanovic via samba wrote: > That's correct, I don't have "Unix Attributes" but through the advanced > view I have access to all attributes. > > The ldbsearch command is not returning anything in my case, it gives me 0 > records - no matter which user I try, even the Administrator. I checked the > command several times to make sure

Hi, I've done samba-tool domain classicupgrade from Samba 3.0.9 NT-style domain to Samba 4.3.11 and have issues with SIDs. I have an old SUSE 9 server with Samba 3.0.9 NT-style domain (only this PDC, no BDC). I migrated this samba configuration to Ubuntu 16.04.1 with Samba 4.3.11 and it worked very well. Then I did inplace upgrade to Samba AD DC domain using the following command:

On Mon, 19 Jun 2017 12:38:09 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > Here is the DC's smb.conf: > > > [global] > workgroup = SAMDOM > realm = SAMDOM.EXAMPLE.COM > netbios name = DC > interfaces = lo br-lxc > bind interfaces only = Yes > server role = active directory domain controller >

On Mon, 2017-10-02 at 09:59 +1300, Garming Sam via samba wrote: > Can you provide a bit more logs? At first glance, it doesn't seem quite > related to group memberships. > I agree, we need more logs here. Turn up the log level and see what the error causing that final error is.   However, take care not to publish confidential details like staff names and sensitive attributes like

Hi All I have a running SAMBA PDC on Debian Jessie on a PowerPC. I have backported Samba 4.3.18 and is working well. I have installed a SDC (if I may use that name) on a different network, the same version of Samba but on a Debian Jessie on AMD64. I followed every instruction in https://wiki.samba.org/index.php/Join_an_additional_Samba_DC_to_an_existing_Active_Directory. So every test

I create domain in Samba AD DC and add user 'cas' and group 'aaa': # samba-tool user list | grep cas cas # samba-tool group list | grep aaa aaa Now I try to add user 'cas' to group 'aaa': # samba-tool group addmembers aaa cas -Uadministrator Added members to group aaa But listmembers does not show this user in group: # samba-tool group listmembers aaa

On Mon, 19 Jun 2017 14:46:34 +0200 Viktor Trojanovic <viktor at troja.ch> wrote: > On 19 June 2017 at 14:20, lingpanda101 via samba > <samba at lists.samba.org> wrote: > > > On 6/19/2017 7:51 AM, Viktor Trojanovic via samba wrote: > > > >> That's correct, I don't have "Unix Attributes" but through the > >> advanced view I have

Thank you Kees. On Mon, 6 Nov 2023 at 09:37, Kees van Vloten via samba <samba at lists.samba.org> wrote: > I am currently running at 4.19.2 but I have run 4.18.6 and 4.18.5. I did > not experience any issues with nested group lookups, which many of the > filters rely on. Interestingly, I've now found that (on my current DCs, running 4.18.5), ldbsearch *does* seem to return the