similar to: Replication, automatic checks

Hai, I snapped this part of you logs. > Successful AuthZ: [DCE/RPC,krb5] user [COMPANY]\[DC6$] [S-1-5-21-2660373802-310620142-1895175072-6626] at [Fri, 26 Apr 2019 10:16:20.224329 PDT] Remote host [ipv4:10.14.16.11:35006] local host [ipv4:10.12.16.11:49153] > [2019/04/26 10:16:23.503632, 0] ../../source4/lib/cmdline/popt_common.c:74(popt_s4_talloc_log_fn) > Bad talloc magic value

Hai Mason,   I had a look at the debug output.   on 1) why around 15-16 second, that i really dont know. im trying to figure that out. on 2) if DNS is inconsistance, that everything is unrelayable. This is really the first the that needs fixing. then we look again at the replication.   The debug output still shows several messages about zones in flat files. I still do believe also that this

Help, my Samba DC's refuse to sync :-( I have 2 Samba 4.1.17 DC servers. I made some changes via Active Directory USer and Computers on Windows. However even after a weekend the changes do not appear on the second DC. If I run samba-tool ldapcmp ldap://dc1 ldap://dc2 -Uadministrator --filter=msDS-NcType,serverState,subrefs I see:

[I did check the Wiki on this, but didn't find anything very definitive. So I'm asking here.] ? I've used "samba-tool drs showrepl" as a check of replication across the AD structure. (We have three DC's, in this case.)? ? Generally I use that tool on a manual basis to make sure replication is working, say after an upgrade etc. ? However, it would probably be good to check

So, I setup Samba on Ubuntu 18.04, using the packaged Samba version. [Thanks Rowland/Louis et al.] I'm doing some testing/tinkering using FreeNAS as a share, using the AD as the authentication back-end. As part of that process, you need to add a computer account and change some security settings. I setup RSAT and can see the AD tree, and add users etc. When I try to switch to advanced view

Hai,???? ? I?have created a new?script for checking samba DC database replications. ? I?have tested with 2 DC's , if there people with more than 2 DCs, and want to test for me, would be great. I tested on debian wheezy, but should work on any apt-get capable os.? ( but not?tested ) ? What it does.. - auto detects the?DC in you network. -?detects the DC met FSMO roles and compairs this

Hai Nico,   Ok great, its fixed, and yes, i do think that the reboot fixed it, dont ask my why, i dont know.. i only know the fix ;-) Seen this few times before..   About the script, did you run it without the password in the script or with the password in the script? So i can check whats wrong there.   Your running samba 4.1.17 ? on which os?   Greetz,   Louis       Van:

A sort of digest reply... RPvs> Not sure, what is a samba4/adc ??? RPvs> Or do you mean a 'Has anybody joined a Samba DC on Ubuntu 18.04' ? Yes, doing an active directory controller [ADC] not just a workgroup-share. [Though, not "joining" a DC already in existance, but creating a new AD setup.] RPvs> If so, then yes and it was hell What exactly was hellish about it?

I was trying to get Samba4 [as a DC] setup on Ubuntu 18.04 However, I'm having quite a lot of difficulty. Has anyone successfully setup a samba4/adc on Ububtu 18.04 - and if so, have a quick walk-through. It would save me a lot of time, I expect. [Yeah, I know 18.04 has been out all of a week, but someone has to go first!] TIA -Greg

Hi, I have built two samba4 boxes, one as a PDC and the as a DC, all working perfectly. If I create a user through the mmc snapin then turn off the PDC, I can still login to the domain using the DC which is great. The problem is their files and ntfs permissions on BDC. I have assigned user and group rights using windows explorer to certain folders, i.e granted user1 full permissions to that

>> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba receive the SIGTERM signal and >> restart even if I remove it from the logrotate configuration. On >>

So, I'm curious about the contrast between modifying netplan vs simply disabling systemd.resolved Is there some advantage to the gyrations to make netplan work, vs simply disabling resolved and manually defining the IP and DNS server? [I'm not complaining, I'm thankful for all the options - just wanting to have the best handle possible on the reasoning behind one method vs the other.]

Am Sa., 6. Apr. 2019 um 18:01 Uhr schrieb Rowland Penny via samba < samba at lists.samba.org>: > On Sat, 6 Apr 2019 17:21:26 +0200 > Martin Krämer <mk.maddin at gmail.com> wrote: > > > Hello Rowland, > > > > thanks for your help. > > Below my comments > > > > See here: > > > > > > http://apt.van-belle.nl/ > > >

Hi all, I'm running in circles trying to debug replication failures on samba 4.7.6: dc00 : is a VM on KVM host (attached to a bridge on local LAN) dc01 : is a similarly configured VM on another KVM host. I've forcibly demoted and re-promoted dc01 but I still cannot get automatic replication to work: root at dc00 ~]# samba-tool drs showrepl Krynn\DC00 DSA Options: 0x00000001 DSA

I went and got the newest (upped recently) script. No love. I removed the email address line to get more command line output. root at dc01:~# ./samba-check-db-repl.sh Running with with console output Running : /usr/bin/samba-tool ldapcmp --filter='whenChanged' ldap://dc01 ldap://dc02.dtsh***m.dt. Please wait.. this can take a while.. Failed to bind - LDAP error 49

Dear Adrian and Ian (and r-helpers), I encountered a curious result in developing an example using the bicreg function in the BMA package: I noticed that pairs of models with equal R^2 and equal numbers of predictors had nevertheless different BIC values. Looking at the bicreg function, the definition of BIC appears to be the usual one, or close to it [bic <- n * log(1 - r2/100) + (size - 1) *

Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children

When I run ./samba-check-db-repl.sh script I am getting the following: root at dc01:~# ./samba-check-db-repl.sh Failed to bind - LDAP error 49 LDAP_INVALID_CREDENTIALS - <SASL:[GSS-SPNEGO]: NT_STATUS_LOGON_FAILURE> <> Failed to connect to 'ldap://dc02.dtsh**m.dt.' with backend 'ldap': (null) ERROR(ldb): uncaught exception - None File

On 6/25/19 11:21 AM, Gregory Sloop via samba wrote: > You can always connect to the SMB share using a domain user/password credential set, even if you're not a member of the domain. > Something like - Connect as: User: "somedomain\pat" with Pat's password. > When we try this from a machine that is not connected to the domain, authentication fails:

RPvs> On Wed, 23 Jan 2019 10:06:52 -0800 RPvs> Gregory Sloop via samba <samba at lists.samba.org> wrote: >> RPvs> Have you read this: >> RPvs> https://wiki.samba.org/index.php/Roaming_Windows_User_Profiles >> RPvs> and possibly, this: >> RPvs> https://wiki.samba.org/index.php/Configuring_Windows_Profile_Folder_Redirections >> RPvs>