Displaying 20 results from an estimated 10000 matches similar to: "messy replication"
2019 Jul 16
0
messy replication
Can you run this on both your DC's
wget https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh
bash samba-collect-debug-info.sh
As im seeing multiple "invalid parameter" message, we need to see more of the setup.
Anonimize the output if needed.
Run this on both DC's : touch /etc/samba/lmhosts
And that lmhosts message is gone.
Greetz,
2019 Jul 16
3
messy replication
I've summerized a bit..
And i saw Rowland also answered already.
Below is anonimized, but it shows, 2 completely different server setups.
I really suggest you setup your AD-DC's the same.
To summ up.
DC1
Samba is running as an AD DC but 'winbindd' is NOT running.
You running SSSD on the AD-DC, which is not supported.
Your using a really out-dated OS..
The hosts is not
2017 Sep 29
4
samba 4.7.0 replication errors
Hallo,
we have 5 ADDCs. All of them did run with sernet-samba 4.6.7.
I updated 4 of them to sernet-samba 4.7.0, one after the other, checked replication, everything seemed to be ok.
One day later a colleague wanted to delete a lot of users with a powershell-script and since then the
replication doesnt work anymore. (Im sure the script is not the problem, but it seemes like it triggered something)
2014 Sep 18
3
samba 4 domain join to win 2008r2 level DC w/ a schema with exchange 2010 extensions: replication after the join is broken
I tried to join a samba4 to a win2008r2 level domain (OS level 2012) running exchange 2010.
The join succeeds but the later replication is broken due to schema differences.
In order to to find the cause, I started a test setup with:
* a win2008r2 DC w/ minimal AD
* upgraded the schema and the OS to 2012 (function level is still 2008r2)
* and added a exchange server to the domain.
And that is
2017 May 10
2
Kcc connection
Hello Christian,
Ive had a quick look at you output, that looks pretty normal.
I'll have a good look Friday, tomorrow day off.
So my suggestion is post the output to the list but -d10 is not needed.
The regular output should be sufficiant.
Im wondering why there is no dc3 in kcc also but why i see over 15 RPC sessions.
Maybe normal maybe not, this i dont know.
Greetz,
Louis
>
2016 Jan 21
2
showrepl is showing a deleted connexion
Hi everybody,
One of my DC crash this afternoon (dead disk).
I can't remove this DC server from windows GUI (computer object from < users and computers >) and NTDS settings from < sites and services > because windows GUI error.
So i manually remove this old server :
- Clean all DNS stuff (tpc, sites, kerberos, kpasswd, srv entries.....)
- With apache directory
2013 Feb 12
1
Replication Ok, or not?
Setup a DC using 4.0.3 - all appears to go fine...
Setup a second DC and everything works fine to here...but I'm not sure
if replication is actually working or not.
Here's what I get from ./samba-tool drs showrepl
I've also done. [./samba-tool drs kcc -Uadministrator
dc2.samba.somedom.local] in an attempt to fix the replication problem.
(or what I think is a problem.)
[The outbound
2014 Jun 17
2
joined DC but replication fails
ubuntu 14.04 DCs
DC1 with fsmo
resolve_lmhosts: Attempting lmhosts lookup for name
51755e44-0a78-4ab8-8206-b4ae8a09c172._msdcs.altea.site<0x20>
dns child failed to find name
'51755e44-0a78-4ab8-8206-b4ae8a09c172._msdcs.altea.site' of type A
DC2
/usr/local/samba/sbin/samba_dnsupdate: update failed: NOTAUTH
resolve_lmhosts: Attempting lmhosts lookup for name
2019 Aug 20
3
Problems with NIS Server on Samba 4
Hi,
I performed the procedures below on Samba4-DC1 (Master) and apparently
everything went fine.
/etc/init.d/samba-ad-dc stop
sed -i -e 's/${DOMAINDN}/DC=empresa,DC=com,DC=br/g' \
-e 's/${NETBIOSNAME}/SAMBA4-DC1/g' \
-e 's/${NISDOMAIN}/empresa/g' \
/tmp/ypServ30.ldif
root at samba4-dc1:/tmp# ldbmodify -H /var/lib/samba/private/sam.ldb
2016 Aug 23
2
samba-tool drs showrepl shows WERR_BAD_NETPATH
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:
2016 Aug 22
1
ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (-1073610699, 'The operation cannot be performed.')
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
2019 Jul 17
2
messy replication
On 16/07/19 15:38, Rowland penny via samba wrote:
>
> You (because of your Samba version) can only demote the DC on the DC
> itself, so just follow the info at the top of the page.
Hello again,
I'm trying to follow instructions for demoting:
https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC
I don't think I need to transfer FSMO roles since both controllers own them:
2019 Aug 30
4
Upgrade Samba 4
Hai,
?
You can safely ignore?that mesage.
?
If both servers are done and running 4.8.? procede to 4.9
?
>> ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such element'
is fixed in later samba versions
?
Greetz,
?
Louis
?
?
?
Van: Marcio Demetrio Bacci [mailto:marciobacci at gmail.com]
Verzonden: vrijdag 30 augustus 2019 11:39
Aan: L.P.H. van Belle
2016 Jan 22
2
showrepl is showing a deleted connexion
Solved !
Thanks for the script.
In my case, it was just too late.
I have just found a ugly but working solution:
From Configuration, Schema, Domaindnszones, forestdnszones and principal, I remove using ldbdel a "repsTo" binary object.
No more trouble with drs showrepl :-)
-----Message d'origine-----
DeĀ : samba [mailto:samba-bounces at lists.samba.org] De la part de Stefan Kania
2016 Jun 07
2
Samba AD member lost domain join after reboot
On 6/7/2016 12:31 PM, Alexis RIES wrote:
> I was wrong, the problem persists, it is not because of the DNS.
> You have the same configuration as me, but with two domains controller ?
>
> On 07/06/2016 18:05, Alexis RIES wrote:
>> I think I found my problem, when configuring my second domain
>> controller, I have created by mistake a round robin DNS entry on
>>
2013 Feb 28
1
[SOLVED] replace Windows 2003 dc]
S?rgio Henrique <sermac at gmail.com> quatschte am Mon, Feb 25, 2013 at 04:26:30PM +0000:
> Solved.
>
> I have sucessfully migrated a windows 2008R2 domain to samba4 and then
> create a new samba domain as a replica.
>
> A lot of steps i had to introduce.
Hi S?rgio,
> 1- Working on DNS
> add samba dc to forest and domain dns _ldap values
> change DNS SOA to
2016 Sep 28
3
samba-tool domain join DC hangs
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
2016 Sep 28
3
?==?utf-8?q? samba-tool domain join DC hangs
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
2019 Aug 12
2
Problems joining Samba 4 in the domain
Ah, so the error changed..
?
Can you try
?
samba-tool domain join empresa.com.br DC -k yes -d 3 --server=samba4-dc01.empresa.com.br?
so we try to join through samba4-dc1 and not the windows DC.
?
Looking at below again.
(objectclass=primaryDomain))' base: 'cn=Primary Domains': No such object: dsdb_search at ../source4/dsdb/common/util.c:4691) and from
2020 Jul 16
2
How to fully remove entries to dead windows server
To save the whole back story, I borked everything and had to restore from
backups.
DC1 and DC2 (Samba DC's) came back fine
DC3 (Windows 2008 DC) did not come back. Which is fine, I wanted to
decommission it anyway.
I have seized all the FSMO roles (because DC3 previously held them all) and
replication SEEMS to be OK (users created on each machine replicate across
instantly, although