similar to: Failing replication

Displaying 20 results from an estimated 700 matches similar to: "Failing replication"

2019 Aug 16
2
Failing to join existing AD as DC
First of all, thanks to you all for bearing with me. To answer the questions: - Subnets: yes, different subnets, routing is fine, can connect to Windows DC via telnet (DNS), OpenSSL on 389 and 636 - Naming: I could not find any object in the existing AD with the same name of the Samba DC that I want to add - Join existing: I try to join an existing Windows AD, not Samba AD I wiped the
2018 Jul 02
0
WERR_BAD_NET_RESP on replication (--full-sync)
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
2018 Jun 21
0
WERR_BAD_NET_RESP on replication (--full-sync)
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, >
2014 Jan 09
0
Samba4/AD Replication Issue
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
2018 Jan 11
0
DRS Replication between two DC's Failing
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 >  
2018 Jan 12
1
DRS Replication between two DC's Failing
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
2018 Jan 11
0
DRS Replication between two DC's Failing
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 >
2018 Jun 21
2
WERR_BAD_NET_RESP on replication (--full-sync)
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:~#
2018 Jun 22
2
WERR_BAD_NET_RESP on replication (--full-sync)
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
2018 Jan 11
4
DRS Replication between two DC's Failing
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 iumsvrpdc DC=iumnet,DC=edu,DC=na --sync-forced -UAdministrator INFO: Current debug levels: all: 9 tdb: 9 printdrivers: 9 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9 idmap: 9
2018 Jan 11
3
DRS Replication between two DC's Failing
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 lanman: 9 smb: 9 rpc_parse: 9 rpc_srv: 9 rpc_cli: 9 passdb: 9 sam: 9 auth: 9 winbind: 9 vfs: 9
2019 Aug 16
0
Failing to join existing AD as DC
On 16/08/2019 14:14, Alexander Harm via samba wrote: > > > > > > 4. apt update &&?apt -t buster-backports install samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user smbclient You are missing the 'acl' package > > 5.?find /var/run/samba /var/lib/samba /var/cache/samba /var/lib/samba/private -name '*.tdb' -name
2020 Feb 07
1
Failing replication
I did but these are the last lines. It ends with ?raise e? also in the shell. I also ran it on the other DCs and they all end with ?raise e?. Alexander On 7. February 2020 at 09:12:02, Andrew Bartlett (abartlet at samba.org) wrote: G'Day Alexander, It looks like you have copied the logs out of a terminal and lost the ends of the lines. Those have the critical (groan...) details of
2019 Aug 16
3
Failing to join existing AD as DC
Ah, OK. Thought that I read this somewhere to first create a DC and then join. So I demote and just try to join straight away? On 16. August 2019 at 15:38:56, Rowland penny via samba (samba at lists.samba.org) wrote: On 16/08/2019 14:14, Alexander Harm via samba wrote: > > > > > > 4. apt update &&?apt -t buster-backports install samba attr winbind
2019 Aug 16
3
Failing to join existing AD as DC
On 16/08/2019 12:05, L.P.H. van Belle via samba wrote: > It's windows that is not allowing samba to join. > > This should make thing more clear in my opinion. > > samba-tool fsmo show -H ldap://$(hostname -d) > And > samba-tool fsmo show -H ldap://10.88.80.88 -U Administrator > > These both work agains my Samba AD-DC's (ldap://$(hostname -d)) > And my windows
2020 Feb 08
3
[PATCH] Re: Failing replication
Hi Andrew, I applied your patch to the Debian packages of Louis. Do you happen to know in which package it will end up? Tried samba and samba-dsdb-modules but the error remains the same. Alexander On 8. February 2020 at 01:38:25, Alexander Harm (alexander.harm at apfel-q.de) wrote: Hi Andrew, you can use my name if you want (Alexander Harm). I will try and build with your patch.
2020 Feb 07
1
[PATCH] Re: Failing replication
Thanks. At this stage is looks like a bug in the repl_meta_data module. Try the attached patch. Can I name you in the bug and is there any affiliation (eg employer) you would like named? I've filed a bug and will file a merge request once I have a test to confirm this. https://bugzilla.samba.org/show_bug.cgi?id=14272 Thanks! Andrew Bartlett On Fri, 2020-02-07 at 23:34 +0100, Alexander
2020 Feb 07
20
Failing replication
Hi Andrew, thanks for your reply. Find attached the output of the command. Looks like it fails on renaming an object to me. Regards, Alexander On 7. February 2020 at 08:50:02, Andrew Bartlett via samba (samba at lists.samba.org) wrote: On Wed, 2020-02-05 at 23:41 +0100, Alexander Harm via samba wrote: > Hello, > > we could need some help resolving a replication issue we
2020 Feb 10
1
[PATCH] Re: Failing replication
Thanks for your invaluable help. I proceeded as advised and installed the patched packages. Still an error though, debug.txt attached. Regards, Alexander On 10. February 2020 at 11:17:02, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: Hai Alexander, I had a quick look, sorry for all the absence but im very buzzy atm with some office work. A quick howto for add this in the
2020 Feb 07
0
Failing replication
G'Day Alexander, It looks like you have copied the logs out of a terminal and lost the ends of the lines. Those have the critical (groan...) details of what went wrong with the apparent 'critical extension' failure. Can you try and get those and I'll look at them tomorrow. Thanks! Andrew Bartlett On Fri, 2020-02-07 at 08:56 +0100, Alexander Harm via samba wrote: > Hi