similar to: NO DNS zone information found in source domain, not replicating DNS

I joined a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000 domain controller as an additional domain controller with the command: samba-tool domain join adi.com DC -Uadministrator --realm=adi.com --dns-backend=BIND9_DLZ The messages indicated that this was mostly sucessfull with the exception of the message: NO DNS zone information found in source domain, not replicating DNS

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

> Submitted bug 11098. Debug level 5 logs are attached to the bug along > with the smb.conf file used. > > I am assuming that the problem is with the Wondows 2000 DC because I > assume that 4.2.0rc4 would not have been made available if it could > not authenticate against any domain controller. > > For us this is a fatal bug. > > > This problem shows up on both

> On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: > > This problem shows up on both Linux and Solaris. I am going to show > > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > > > We are using 'security = domain' with a Windows 2000 domain controller. > > We are setting 'password server = starfish2' dispite the fact that the > >

> > On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: > > > This problem shows up on both Linux and Solaris. I am going to show > > > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > > > > > We are using 'security = domain' with a Windows 2000 domain controller. > > > We are setting 'password server = starfish2'

>>> On Thu, 2015-02-12 at 11:44 -0500, Thomas Schulz wrote: >>>> This problem shows up on both Linux and Solaris. I am going to show >>>> the logs from a Fedora 2.6.25-14.fc9.i686 machine. >>>> >>>> We are using 'security = domain' with a Windows 2000 domain controller. >>>> We are setting 'password server =

hi again, now the join finished but ... i have a high CPU load caused by a samba-process. Samba is consuming 100% of one CPU and the replication fails. Is my AD to large???? root at dc2:# samba-tool drs showrepl Default-First-Site-Name\DC2 DSA Options: 0x00000001 DSA object GUID: e9d31c7e-acb3-4473-823a-39b06ab9fa95 DSA invocationId: 49a80da8-975f-49ef-834b-224b2bbf0805 ==== INBOUND

Hi Denis, yes, the problem initiated after changing the primary group of all my 11034 users. I changed the primary group to different groups. This caused that now every user is member of the LDAP object "Domain users" ldapsearch -LLL -x -h dc1 -x -b "cn=domain users,cn=users,dc=example,dc=net" member | grep ^member: | wc -l 11034 After this action the replication

Hi, the only thing i did, was to assign every user to a ohter group. After this i changed the primary group to this new groups and the samba-server itself assigned the users to the group "domain users"automatically (attribute: member). Now i try to revert this and to rechange the primary group to 513. So i can have again a Domain users object with small number of members. Thanx

Hi Heinz, > > yes, the problem initiated after changing the primary group of all my 11034 users. > > I changed the primary group to different groups. This caused that now every user is member of the LDAP object "Domain users" > > ldapsearch -LLL -x -h dc1 -x -b "cn=domain users,cn=users,dc=example,dc=net" member | grep ^member: | wc -l > 11034 > >

I'm receiving an error that the TAPI3Directory cannot be replicated. However, the GUID or Distinguished name cannot be found in the Directory. (Including in "Deleted Objects".) Error joining to domain: Schema-DN[CN=Schema,CN=Configuration,DC=MainOffice,DC=local] objects[402] linked_values[0] Schema-DN[CN=Schema,CN=Configuration,DC=MainOffice,DC=local] objects[804] linked_values[0]

Hi there, Im trying to join a samba 4.0.1 server to an older samba 4 alpha 17 server. Whatever i do the join is interrupted but i dont know what goes wrong. Dns is double checked and correct as is most other stuff. How can i get a better view of what is happening than this? Can it be the source domain that contains erroneous objects? My goal is to move the old server to a new one, maybe there

Hi Heinz, > now the join finished > > but ... i have a high CPU load caused by a samba-process. Samba is consuming 100% of one CPU and the replication fails. you have quite a few objects (>12000) in you main partition. Do you have a large group with all those objects inside? The commit of large group used to result in very very long commit time. There should have been some

can you provide more info. like: OS running? samba version? Samba package or from source? samba AD DC version and OS? If there is and smb.conf when you join, remove it or rename it and try joining again. Greetz, Louis >-----Oorspronkelijk bericht----- >Van: sarah.leecb at gmail.com >[mailto:samba-bounces at lists.samba.org] Namens Sarah Lee >Verzonden: maandag 15 juni

Hi list, i removed my second DC from the domain, and now the re-join as DC hangs. the join hangs now for ca. 2 hours at the step "Committing SAM database" version: samba 4.5.0 on ubuntu 14.04 with a "strace -p " i see this: strace -p 1793 Process 1793 attached brk(0x35e18000) = 0x35e18000 brk(0x35e39000) = 0x35e39000

Is there any idea why Samba does not join the domain in the DC role? By the way, to compile samba us need packages bind-utils libblkid-devel libsemanage-python libxml2-devel perl- Test-Base policycoreutils-python gcc gdb openldap-devel python- devel readline-devel audit-lib s- python checkpolicy libcgroup libselinux-python libselinux- utils mailcap perl-Algorithm-Diff

Hi all. It's great to see Samba4 has gone generally available. ? I am trying to set up a Samba4 server to connect to an existing Windows domain with a windows AD server. I am able to follow the instructions here: https://wiki.samba.org/index.php/Samba4/HOWTO#HOWTO_to_set_up_a_AD_DC I can download using git. Compile. Make. And install. This seems to all work. I then follow the instructions for

Thanks Rowloand for the hint! I installed sernet-samba 4.7 and give it a try. Now I get: [root at dc-12 1]# samba-tool domain join obel.lan DC --realm=obel.lan -Uadministrator Finding a writeable DC for domain 'obel.lan' Found DC dc-11.obel.lan Password for [OBEL\administrator]: workgroup is OBEL realm is obel.lan Adding CN=DC-12,OU=Domain Controllers,DC=obel,DC=lan Adding

I wanted to do a little playtesting with Samba as a domain controller. I spun up a Debian 10 box, installed Samba (package 4.9.5+dfsg-5+deb10u1) , and attempted to join it to the domain. It crashed horribly. ;) Unfortunately their domain ends in ".local". There's nothing I can do about it at the moment. But I do remove multicast DNS from nsswitch to prevent it from attempting to