similar to: skip chunk if "DRS linked attribute for GUID - DN not found"

On Tue, 2017-06-13 at 12:01 +0000, Andrej Gessel via samba wrote: > Hello everyone, > > i try to use Samba RODC(4.6.5) with W2K8R2. Windows AD has around > 35000 objects. My Samba machine is small one (ARM 32bit CPU) with > only 2GB physical memory, so i can’t join to the domain because of > expensive memory usage. > To solve this Problem, i decide to replicate only critical

Hello, i have a samba4 ad domain with 5 domain controllers. Since 2-3 weeks, i have problems with kerberos, log.samba: [2012/11/16 16:21:11, 1] ../source4/auth/gensec/gensec_gssapi.c:645(gensec_gssapi_update) GSS server Update(krb5)(1) Update failed: Miscellaneous failure (see text): Decrypt integrity check failed [2012/11/16 16:21:12, 2]

I have a very old domain i inherited that is running samba 4.5.6 but is on schema version 30. I added a windows 2003 DC and used the 2008r2 adprep.exe utility to upgrade the schema to version 47. To do so the 2003 server had to take the schema and infrastructure roles. I am now trying to use the repadmin utility to sync the schema back to samba to it is failing with the following: [2017/06/09

I joined the windows 2019 domain, where among the controllers there is a Samba DC version 4.8.5, and after that the replica stopped working windows servers <--> samba DC. Upgrading to version 4.9.4 did not help Errors: ``` фев 12 14:15:28 srv-dc01 samba[24637]: [2019/02/12 14:15:28.679872,  0] ../source4/dsdb/repl/replicated_objects.c:248(dsdb_repl_resolve_working_schema) фев 12

Yep, I did. SPN of newly added DC were missing on all DC except for the newly added DC. I expect SPN are created on joined DC then replicated on others DCs. Adding SPN for that newly added DC in DIT of FSMO owner does not helped much. Now the error is coming repetitively in newly added DC is: [2015/11/16 16:49:42.529374, 0]

Do you tnink I can simply apt-get install from that repo to upgrade the current samba? Going down the demote/re-join route, I'm encountering problems demoting the DC: Deactivating inbound replication Asking partner server DC1.mydomain.local to synchronize from us Error while demoting, re-enabling inbound replication ERROR(<class 'samba.drs_utils.drsException'>): Error while

Hello, I upgrade the schema for our main ADDC and everything works properly, but the member DC (DC to an Existing AD) fails. Both servers are in version 4.10.2 Distro: Debian 9.8 *Main ADDC:* [2019/04/16 15:43:03.814846, 0] ../../source4/rpc_server/drsuapi/getncchanges.c:2919(dcesrv_drsuapi_DsGetNCChanges) ../../source4/rpc_server/drsuapi/getncchanges.c:2919: DsGetNCChanges 2nd replication

We've joined an RODC to the domain (Windows 2008R2 running a W2003 FFL/DFL AD) but are getting these errors on first startup. It was joined with: samba-tool domain join main.adlab.netdirect.ca RODC --realm=main.adlab.netdirect.ca --username=administrator at main.adlab.netdirect.ca --dns-backend=BIND9_DLZ but we get these errors right after startup: Nov 28 12:35:27 sles-bree samba[3939]:

On Tue, 12 Feb 2019 14:28:44 +0500 Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > I joined the windows 2019 domain, where among the controllers there > is a Samba DC version 4.8.5, and after that the replica stopped > working windows servers <--> samba DC. Upgrading to version 4.9.4 did > not help > > Errors: > > ``` > > фев 12

Hi, This is a known issue: https://bugzilla.samba.org/show_bug.cgi?id=12204 https://bugzilla.samba.org/show_bug.cgi?id=13713 There are currently patches in master to fix this issue. We could probably backport a patch to 4.10, but you'd have to rebuild Samba. Alternatively, re-joining the domain controller (or joining a new DC and demoting the old one) probably works because I believe there

Hi, I'm experiencing a strange replication problem. Context: 5 samba DC in a single domain FSMO roles are owned by 10.0.10.11 (vs-dc-siege-001) vs-dc-siege-001: 10.0.10.11 vs-dc-siege-002: 10.0.10.12 vs-dc-vty-001: 10.0.100.11 vs-dc-vty-002: 10.0.100.12 vs-oc-vty-001: 10.0.100.156 I get the following errors in : samba-tool drs showrepl CN=Configuration,DC=corp,DC=mydomain,DC=fr

Hi, While I think we have most of the 2012 schema problems under control now, there's still quite a bit of work to get the functional level things working. In order to actually raise the level, we still need to implement a number of features (mostly security). We're able to do some prep steps (so that things like Windows server 2012 R2 appear to join us but still use 2008 R2 FL) but

On Tue, 12 Feb 2019 12:21:29 +0100 Viktor Trojanovic via samba <samba at lists.samba.org> wrote: > > On 12.02.2019 11:16, Rowland Penny via samba wrote: > > On Tue, 12 Feb 2019 14:28:44 +0500 > > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > > > >> I joined the windows 2019 domain, where among the controllers there >

Thanks Rowland and Garming for your help!! How about "another DC", or 'a second DC' ? Ok. Got it! :D Alternatively, re-joining the domain controller (or joining a new DC and > demoting the old one) probably works because I believe there is code to > handle this case. I re-joined (remove secrets.tdb and .lbd, copy idmap from existing DC...) and now works properly!

On 12.02.2019 11:16, Rowland Penny via samba wrote: > On Tue, 12 Feb 2019 14:28:44 +0500 > Шигапов Денис Вильданович via samba <samba at lists.samba.org> wrote: > >> I joined the windows 2019 domain, where among the controllers there >> is a Samba DC version 4.8.5, and after that the replica stopped >> working windows servers <--> samba DC. Upgrading to

Hi, Everything seems to be ok, but the following is happening now. When I put a new computer in the domain, it only appears in the "second DC" and does not replicate to the first DC. root at dc3:~# samba-tool computer list |grep MINT-TESTE root at dc3:~# root at dc4:~# samba-tool computer list |grep MINT-TESTE MINT-TESTE$ root at dc4:~# Any idea? On Wed, Apr 17, 2019 at 8:12 AM

Hello. I've got a network of FreeBSD servers which traditionally hosted a classic domain. I upgraded some months ago, removing the old PDC and BDC and migrating to an AD DC controller in a jail. This is working fine with Samba 4.4.13. Now I'm trying to add a second DC, so I created a new jail on another physical server and went on with the setup, following: >

Hello, If when joining the computer in the domain and at the moment who received the request was the "second DC", it should automatically synchronize with the "first DC", correct? On Wed, Apr 17, 2019 at 5:00 PM Elias Pereira <empbilly at gmail.com> wrote: > Hi, > > Everything seems to be ok, but the following is happening now. > > When I put a new

Hello, Thanks for the feedback Garming!!! 👍 On Wed, Apr 17, 2019 at 12:35 AM Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > While I think we have most of the 2012 schema problems under control > now, there's still quite a bit of work to get the functional level > things working. In order to actually raise the level, we still need to > implement a number of

Hi all, I have 3 DCs running Samba 4.3.1 in the same domain. They seem to work quiet well with coherent databases on each of them. After rebuilding my RPM to include systemd units, I've joined a Samba 4.3.1 today, using --domain-critical-only. The join was successful, the replication was not. This DC has only 146 objects in the DB when it should have a bit less than 50000 objects. As I was