similar to: 2 Samba 4.1 DCs: demote fails with Python traceback

Hi together, Demoting from a Win-Server-Based Active Directory fails root at srvf01:~# samba-tool domain demote --server windc-server -UAdministrator Using srv15.lan.compumaster.de as partner server for the demotion Password for [COMPUMASTER\Administrator]: Desactivating inbound replication Asking partner server windc-server to synchronize from us Error while demoting, re-enabling inbound

I have a server that is not replicating correctly, but passes all the tests listed here: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC In particular running # host -t CNAME 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us 976c9c86-288d-483e-baec-7043a9c4a6cd._msdcs.ncs.k12.de.us is an alias for ncssamba2.ncs.k12.de.us. returns correct information on all DCs.

Hi Chris, Le 22/03/2016 22:07, Chris Hastie a écrit : > I'm trying to remove a DC from a Samba4 based AD network, but run into > an error that I can't fathom. Can anyone point me in the right direction? > > # samba-tool domain demote -Uadministrator which version of samba are you using? 4.4 or below? is the sogo3.ad.oak-wood.co.uk server still running ok or do you have

I'm trying to remove a DC from a Samba4 based AD network, but run into an error that I can't fathom. Can anyone point me in the right direction? # samba-tool domain demote -Uadministrator GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'spnego' registered GENSEC

I started with one dc, 'dc1', running samba v4.0.21, in subnet1. I successfully added two more dc's, 'dc2' and 'dc3', both running samba v4.0.24, both in subnet2. There are several firewalls between subnets 1 & 2. I continued to make firewall holes on behalf of msad after I added dc's 2 & 3. I.e. when they were added, there were patterns of communication

Hi, I have 2 DC Samba 4 in my network. My new DC is Samba 4.6.3 My Old DC is Samba 4.2.1 I want demote my DC (old) with Samba 4.2.1, but the following message appears: ~# samba-tool domain demote -Uadministrator Using dc1.empresa.com.br as partner server for the demotion Password for [EMPRESA\administrator]: Deactivating inbound replication Asking partner server dc1.empresa.com.br to

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

Hai Tom, Sure, you can apt-get install from that repo. You have 3 options. 1) http://apt.van-belle.nl/ the apt repo. Use it like any apt repo. Info on the site. 2) http://downloads.van-belle.nl/samba4/samba-4.5.3/ and use the installer This is when you want to get packages localy in you network and when you want to keep one version, and/or distribute this internaly. The installer script

Hi, Many of these syncing problems were solved in Samba 4.7 (and probably a few more in 4.8). There were a number of unresolved locking issues that we uncovered as well as some inconsistencies with Windows replication. I would try join a DC with one of the latest Samba versions and see if your problems persist. Cheers, Garming On 21/06/18 21:35, Chris Lewis via samba wrote: > Hello, >

I added three DCs to a single DC Samba4 AD domain. They initially replicated and came up - but replication does not appear to be ongoing. A change made to a user via MMC connected to one DC does not appear on another DC. It the logs I see bursts of the following message: [2014/08/12 15:08:08.026270, 0] ../source4/librpc/rpc/dcerpc_util.c:660(dcerpc_pipe_auth_recv) Failed to bind to uuid

On 1/11/2018 1:57 PM, Harsh Kukreja wrote: > Hi > > I have tried  using FQDN for DC1 and DC2 but still it is > failing.Please assist to fix > > samba-tool drs replicate iumdcdp01.iumnet.edu.na > <http://iumdcdp01.iumnet.edu.na> iumsvrpdc DC=iumnet,DC=edu,DC=na > --sync-forced -UAdministrator > INFO: Current debug levels: >   all: 9 >   tdb: 9 >  

What does the WERR_BAD_NET_RESP means? I'm currently upgrading our DCs to 4.8.3 and I've noticed that the off-site DC has a sync problem of the CN=Configuration NC. The FSMO DC is still in the 4.5.5, but all other DCs, including the off-site are already on 4.8.3. Trying to sync the off-site DC with one of the updated DCs does not work either. The WERR_BAD_NET_RESP message already

Hi James Thanks for your response. hots -t A iumsvrpdc (use it's fqdn as well) I have verified it with the FQDN which says that the record iumsvrpdc.iumnet.edu.na exists Search for 'iumsvrpdc' objectGUID ldbsearch -H /usr/local/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid : it shows 2 records found # record 1 dn: CN=NTDS

Hello, We have a Windows 2008 DC (inview-dc1 and a samba 4.4.16 (inview-dc2) server as a backup DC. The system for the most-part works OK, but occasionally the Samba DC goes wildly out of sync (with respect to group membership), normally after a change to a large group. I have noted previously before the out-of-sync event occurs, this command always fails thus : root at inview-dc2:~#

I have a couple of Samba4 AD DCs replicating with Windows Server 2008 DCs. This has been sort of finicky, but I've managed to get it to work (mostly) for several weeks. However, I'm now having an issue where one of my Samba4 DCs will not replicate from any of the other DCs (Windows or Samba) in the domain (Error is WERR_BAD_NET_RESP). Replication output is below. If anyone has ideas of

On 1/11/2018 10:39 AM, Harsh Kukreja via samba wrote: > Hi > > The DRS sync between two Domain Controllers connected on one network is > failing. I have enabled the log level 9. > > samba-tool drs replicate 172.16.10.5 iumsvrpdc DC=iumnet,DC=edu,DC=na > --full-sync -UAdministrator > INFO: Current debug levels: > all: 9 > tdb: 9 > printdrivers: 9 >

OK, tried that. Kicked myself for not trying earlier... but it didn't work. In fact, the error has got worse. Now when I try to go from Genesis to Luke I get: sudo samba-tool drs replicate luke genesis DC=kcs,DC=local -Udomainadmin . . ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (1359, 'WERR_INTERNAL_ERROR')

Thanks Garming. We currently use a standalone bind DNS server. Will the later version of samba work without the integrated DNS backend? Cheers Chris On 21/06/18 23:41, Garming Sam wrote: > Hi, > > Many of these syncing problems were solved in Samba 4.7 (and probably a > few more in 4.8). There were a number of unresolved locking issues that > we uncovered as well as some

I have DC on samba 4.5.2 (pdc) Also I have additional DC on Win2008 R2. (bdc) pdc and bdc just host names When I trying to replicate samba to windows: pdc:~ # samba-tool drs replicate bdc pdc DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ # samba-tool drs replicate bdc pdc CN=Schema,CN=Configuration,DC=tidykzn,DC=local Replicate from pdc to bdc was successful. pdc:~ #

G'day All, I've been setting up a new set of DCs, using 4.2.3 and all was going well until I tried to get a 4th DC going. I'm using bind_DLZ, and I think this is where I went wrong. I provisioned the new DC before having set up bind properly (I forgot to "yum install bind bind-util bind-libs") before hand. The provision worked okay, except that it told me