similar to: replication upper-lower case

Hi, I have set up a fresh DC from scratch using samba 4.5.1 with Bind9, added another DC, all strictly following the instructions in the samba wiki. Samba was built from the source tarball on debian/raspbian 8u8 (Jessie), Bind9 is 9.9.5-9 coming with the OS. Everything appears to be in a working order: I can join Windows workstations, add Users with RSAT, etc. Only when comparing the

sorry, samba version 4.5.0 Am Freitag, 30. September 2016 10:31 CEST, Rowland Penny via samba <samba at lists.samba.org> schrieb: > On Fri, 30 Sep 2016 10:20:27 +0200 > Heinz Hölzl via samba <samba at lists.samba.org> wrote: > > > Hi, > > > > i transfered the roles from DC2 to DC1: > > > > root at dc1:~# samba-tool fsmo transfer

ok, a other try .. i tranfer the roles back to DC2: first run: error second run: error third run: NO error then i added "import samba.drs_utils" in /opt/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py and now the role transfer works fine. root at dc2:~# samba-tool fsmo transfer --role=all -U administrator FSMO transfer of 'rid' role successful FSMO

Heinz, I had exactly the same problem, and used ldbedit to apply the fix. Thanks for digging into this! Now I'm interested in the root cause as well ... Uli Am 16.01.2018 um 16:48 schrieb Heinz Hölzl via samba: > no, it seems to work!!! > > > i did a ldapmodify on DC2: > > ldapmodify -x -h dc2 -D cn=administrator,cn=users,dc=test,dc=net -W -f > serverReference.ldif

Hi, there is no firewall, all DCs are in the same subnet. here ist the output of a test, you can see, the CNAME guid entries in the _msdcs can be resolved on any DC: (DC1 and DC2 are the first and second DCs, SAMBA3 was added at last. ldbsearch -H /srv/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid # record 1 dn: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-

Hi, i transfered the roles from DC2 to DC1: root at dc1:~# samba-tool fsmo transfer --role=all -U administrator This DC already has the 'rid' FSMO role This DC already has the 'pdc' FSMO role This DC already has the 'naming' FSMO role This DC already has the 'infrastructure' FSMO role This DC already has the 'schema' FSMO role This DC already has the

-------- Original-Nachricht -------- Betreff: Re: [Samba] ?= unable to upload printer drive Datum: Mittwoch, 07. Dezember 2016 09:08 CET Von: Heinz Hölzl <heinz.hoelzl at gvcc.net> An: "Rowland Penny" <rpenny at samba.org> > > Hi, > > > > > Follow this wiki page: > > > > > >

hi, there are just 2 bug-rports: https://bugzilla.samba.org/show_bug.cgi?id=12399 https://bugzilla.samba.org/show_bug.cgi?id=12302 Regards, Heinz Am Donnerstag, 17. November 2016 00:00 CET, Norbert Hanke via samba <samba at lists.samba.org> schrieb: > Hi, > > I have set up a fresh DC from scratch using samba 4.5.1 with Bind9, > added another DC, all strictly following

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

Hi! I have a problem with gpupdate having a trust with a M$ -ADS domain. Before creating the trust gpupdate worked fine. Then i added the trust and then gpupdate gives the following error: Updating policy... Computer Policy update has completed successfully. User Policy could not be updated successfully. The following errors were encount ered: The processing of Group Policy failed. Windows

Hi, > Follow this wiki page: > > https://wiki.samba.org/index.php/Setup_a_Samba_print_server#Setup_the_.5Bprinters.5D_share > Then the page you referred and use windows ACLs not posix ACLs done > > I also take it you have given your users & groups uidNumber or > gidNumber attributes. yes, this is a test-environment and i have given the unix-id to administrator,

Hello there, I have a problem with replication between two domain controllers, dc1 and dc2. Distribution: Debian 8.5 Samba-Distribution: sernet-samba 4.3.11-14 The replication on dc2 working fine without any failures. But the synchronization on dc1 gives the failure "WERR_BAD_NETPATH". Because the message "BAD_NETPATH" I checked the DNS-resolution:

Hi All, since Friday I get a surprising error, when I try to replicate my domain-controllers. This is new! It worked before in any direction without any failures... When I replicate from dc2 to dc1 this runs also, without any failures: root at dc1:~# samba-tool drs replicate dc1 dc2 DC=mydomain,DC=uni-frankfurt,DC=de Replicate from dc2 to dc1 was successful. Only when I try to replicate from

hi again. after some tests, (on my operational domain and on a new testdomain) i detected this behavior: on samba 4.11.6 sometimes the new DNS-records finisches on a wrong dns zone. the problem occurs, if more then 5 records are created with the same name in more then one domain zone for example: testa1.jupiter.mydom.org testa2.jupiter.mydom.org testa3.jupiter.mydom.org

Hai Christian, > Can someone reproduce this? No, tried, but sorry, works fine for me on my 4.11.6 server. And what is you try it like this. samba-tool dns add dc1.zone1.domain.de 0.168.192.in-addr.arpa 157 PTR zone1.domain.de -U Administrator samba-tool dns add dc1.zone1.domain.de 1.168.192.in-addr.arpa 157 PTR zone2.domain.de -U Administrator I tested on my production where i have 6

Hi list, i have a samba member-server in a samba4-AD with cups. cups works fine, i can print the testpage from cups and from a windowsclient. but, i am not able to upload a printer driver to a samba4 print-server: i followed this howto: https://wiki.samba.org/index.php/Configuring_Point%27n%27Print_automatic_printer_driver_deployment in printmanagement.msc i can add the server, and i can see

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

Hello Samba Friends, I have a single DC (we'll call it, "DC1") that simply will not take my password when I run this command:? #samba-tool ldapcmp ldap://dc2 ldap://dc3 -Uadministrator? Or this command:? #samba-tool ldapcmp ldap://dc1 ldap://dc2 -Uadministrator? I basically get this:? > Password for [SAMDOM\administrator]:? > Password for [SAMDOM\administrator]:?

Thank you, Louis, for your reply. By simply asking me to provide outputs of the aforementioned files, I found the cause of my first problem (auth failing). It was my /etc/hosts file on dc1. All of them should look like this, and indeed DC2 and DC3's *did* look like this: # cat /etc/hosts > 127.0.0.1 ? ? ? localhost.samdom.mycompany.net ?localhost > 192.168.3.201

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 > >