similar to: restarting samba using a cron job on Debian

Thanks Rowland, for the thoughts. > If you are running Samba4 as an AD DC, you should never start the nmbd > deamon, you should also never start smbd manually. Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but in fact this is what /etc/init.d/samba does. The messages with "AD DC daemon" are generated by that script, and it is the failing one. > What

> Why bother with all the above, just use samba-ad-dc instead. Yes, I streamlined the script somewhat. Let's see what happens when replication fails next time. > You are going to have to supply more info, is there anything in the logs > when replication fails? > If not, try raising the log level until you do get something. Anything specific I should look for? As said it

On 30/11/15 10:01, Lars Hanke wrote: > For some reason my secondary DC loses sync every once in a while. It > looks like this in samba-tool drs showrepl: > > Last attempt @ Thu Nov 19 13:53:09 2015 CET failed, result 5 > (WERR_ACCESS_DENIED) > 229 consecutive failure(s). > Last success @ Wed Nov 18 18:48:07 2015 CET > > Restarting samba fixes the issue for an

On 30/11/15 12:35, Lars Hanke wrote: > Thanks Rowland, for the thoughts. > > > If you are running Samba4 as an AD DC, you should never start the nmbd > > deamon, you should also never start smbd manually. > > Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but > in fact this is what /etc/init.d/samba does. The messages with "AD DC >

The same happens to me on Debian 7 with the included Samba 4.1.17. Although relates to Ubuntu, this is the same issue: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1357471 I can tell you that what triggers this are network connectivity issues between the DCs, even if they last a couple of seconds. Once the connectivity is restored, the replication stays broken unless Samba is restarted.

Hi Marc, >> The cause is that the password change didn' reach both AD DCs, but only >> one. The other one still had the old value as could be seen by >> samba-tool ldapcmp. Restarting the DCs and waiting for a couple of >> seconds brings them back to sync and Windows logons work as they used to. >> Any idea, what I should do next time to obtain valuable output

Hi Guys, I have now updated to 4.5.0 - thank you to all the team for your efforts on this :) I was excited to read in the release notes that there were many replication improvements, and I have run 'samba-tool dbcheck --cross-ncs --fix' on all my DCs; there were many, many replPropertyMetaData and other errors which have now been found and fixed - thanks! However, I think something

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

Hi! I have 2 DC, now add one more DC, but all dcs dont view between they. New DC is "DC2" DC1 - vlan10 -> OK to DC3(Connectad by openvpn) DC1 -> vlan10 -> OK to DC2(vlan50) DC2-> vlan50 -> OK to DC1(vlan10) DC2-> Openvpn -> Dont "see" DC3 DC3 -> Openvpn -> OK to DC1(vlan10) DC3 -> Openvpn -> Dont "view" DC2(vlan50) All version

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

Hi. Here is my problem. I have 2 DC (DC1, DC2) From DC1 I run samba-tool drs showrepl DC1 ------------------------------------------------------------------------------------- INBOUND NEIGHBORS : OK OUTBOUND NEIGHBORS : OK ==== KCC CONNECTION OBJECTS ==== Connection -- Connection name: 179ef6ba-a138-46d7-9a64-880ab4608b04 Enabled : TRUE Server DNS name :

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

Hai, ? when i test my DRS replication, with : samba-tool drs showrepl ms249-lin-007 i have no errors looks ok but, im seeing this as last. ? ==== INBOUND NEIGHBORS ==== 5 connections 0 failure. ? ==== OUTBOUND NEIGHBORS ==== 3 connections 0 failure. ? ==== KCC CONNECTION OBJECTS ==== ? Connection -- ??????? Connection name: 3aa92d11-3cc7-4afd-9975-f0f7d2c5013f ??????? Enabled??????? : TRUE

Thanks Andrew. No - it was my fault for including an easily-solved side query in the same email as the main query.. :) I haven't solved the original issue, which is that 'samba-tool drs showrepl' runs on two of my DCs but not on the third. I don't know if anything else also doesn't work, e.g. some aspect of replication I haven't observed yet - but the only problem I can

I removed a DC using the DC removal tool mentioned in http://gallery.technet.microsoft.com/scriptcenter/d31f091f-2642-4ede-9f97-0e1cc4d577f3 as https://bugzilla.samba.org/show_bug.cgi?id=10734 prevents normal DC demotion. The DC was still all over in DNS, so I had to pick it out. Now replication between the remaining three DCs is broken [root at larkin26 ~]# samba-tool drs showrepl

Hi! Thanks for answer. But, i allowed all ports in my firewall... I tested, shutdown  my DC1 DC2 dont comunication with DC3 I create user in DC2, dont replication with DC3... I waited more in 20 minutes Why ?? Regards; On 17-05-2018 12:01, lingpanda101 wrote: > On 5/17/2018 10:30 AM, Carlos via samba wrote: >> Hi! >> >> I have 2 DC, now add one more DC, but all dcs

Hai,   Question..   2 DC's.  ( debian stretch samba 4.7.5 ) .   DC1 upgraded,  ( DC with FSMO roles)   samba-tool dbcheck --fix samba-tool dbcheck --cross-nc --fix   That fixed on DC1  6 errors. samba-tool drs showrepl show no error.   login on DC2. upgraded. samba-tool drs showrepl show no error and is in sync. samba-tool dbcheck --fix  shows 16 errors   uhm, synced, but not synced..   

Hi Denis, I have seen in an old post that you have tested new KCC from full mesh to bridge head at a french school. Is your "drs showrepl" correct on such DC's ? In my case, a drs showrepl is showing a full mesh on inbound and outbound (not good) but only 1 KCC connection objects (good) Where is a full description of my trouble:

Hi, for a while I am getting the error message Default-First-Site-Name\MACY DSA Options: 0x00000001 DSA object GUID: 0178f264-745f-4478-8858-765947178966 DSA invocationId: f43943f8-11c7-4bd3-8fcc-fa626ff17ff2 ==== INBOUND NEIGHBORS ==== ERROR(runtime): DsReplicaGetInfo of type 0 failed - (-1073610699, 'The operation cannot be performed.') when running samba-tool drs showrepl on one

yes i realized that there is something wrong with BIND9_FLATFILE while encountering with samba_upgradedns -h which doesn't show BIND9_FLATFILE Any help on*drs repl* not working i think it is pointing to wrong FQDN how do i correct that ? > >/ Not able to to view replication.(samba-tool drs showrepl) > />/ > />/ > />/ [root at dc2