Displaying 20 results from an estimated 7000 matches similar to: "replication fails"
2019 Mar 13
3
replication fails
On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba wrote:
> Hi Stefan,
>
> Debian 8 ? 9?
> DC's samba version ?
>
> Can you post your smb.conf and resolv.conf
>
> If you check with (per server what is the outcome. )
> samba-tool dbcheck
> samba-tool dbcheck --cross-nc
>
> You could do a forced sync of a good server to the bad one.
>
2019 Mar 14
2
replication fails
On Thu, 2019-03-14 at 07:38 +0000, Rowland Penny via samba wrote:
> On Wed, 13 Mar 2019 23:59:29 +0000
> Sérgio Basto via samba <samba at lists.samba.org> wrote:
>
> > On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba
> > wrote:
> > > Hi Stefan,
> > >
> > > Debian 8 ? 9?
> > > DC's samba version ?
> > >
2019 Mar 14
0
replication fails
On Thu, 14 Mar 2019 18:10:00 +0000
Sérgio Basto <sergio at serjux.com> wrote:
> On Thu, 2019-03-14 at 07:38 +0000, Rowland Penny via samba wrote:
> > On Wed, 13 Mar 2019 23:59:29 +0000
> > Sérgio Basto via samba <samba at lists.samba.org> wrote:
> >
> > > On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba
> > > wrote:
> >
2019 Mar 14
0
replication fails
On Wed, 13 Mar 2019 23:59:29 +0000
Sérgio Basto via samba <samba at lists.samba.org> wrote:
> On Wed, 2019-03-13 at 11:22 +0100, L.P.H. van Belle via samba wrote:
> > Hi Stefan,
> >
> > Debian 8 ? 9?
> > DC's samba version ?
> >
> > Can you post your smb.conf and resolv.conf
> >
> > If you check with (per server what is the
2019 Mar 13
4
replication fails
Am 13.03.19 um 11:22 schrieb L.P.H. van Belle via samba:
>
> Hi Stefan,
>
> Debian 8 ? 9?
> DC's samba version ?
Deb 9.8, Samba-4.8.9
> Can you post your smb.conf and resolv.conf
>
> If you check with (per server what is the outcome. )
> samba-tool dbcheck
0 errors
> samba-tool dbcheck --cross-nc
Checked 3754 objects (3174 errors)
on the DC1.
where
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
?? And we did compair this months ago..
You did say, everything is in sync now.
Ahhh... ;-)
If you really want to know if you DC's are setup the same.
Tip.. Copy /etc of both server into a new folder.
And runn diff -r /etc-dc1/ /etc-dc2/ > check-me.txt
And check-me.txt
I just did that on my brand new Buster proxy servers, 2 with keepalived.
I'm almost done with this, you
2019 Jul 31
5
GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 15:59 schrieb L.P.H. van Belle via samba:
> Ok, after that reboot
>
> ! Note, atm dont care about secrets.keytab (yet)
> .. I was a bit ahead with things...
>
> One thing at a time, for the keytab to be corrected, you need a perfect correct working
> A PTR CNAME GUIDs for the DC(3) first then we start thinking in kerberos corrections.
>
> Run
2020 Mar 06
3
DCs from 4.10.x to 4.11.x
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Stefan G. Weichinger via samba
> Verzonden: vrijdag 6 maart 2020 10:41
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] DCs from 4.10.x to 4.11.x
>
> Am 06.03.20 um 10:11 schrieb L.P.H. van Belle via samba:
> > After upgrade indexing is done as far i know.
2019 Jul 31
2
GPO issues - getting SYSVOL cleaned up again
I forgot.
dig a pre01svdeb02.pilsbacher.at @192.168.16.205
dig a pre01svdeb02.pilsbacher.at @192.168.16.206
Can you run these also for me.
And there are no CNAMEs pointing to the AD-DCs ?
2020 Mar 06
3
DCs from 4.10.x to 4.11.x
Aah.. Sorry typo.
systemctl unmask samba-ad-dc (umask / unmask )
systemctl enable samba-ad-dc
systemctl start samba-ad-dc
Im very buzy, so slow in responce atm, but if a service fails to upgrade and starts it gets masked.
Unmasking is needed then. To make sure its all enable i also run extra enable.
> -----Oorspronkelijk bericht-----
> Van: Stefan G. Weichinger [mailto:lists at
2019 Jul 31
4
GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 10:47 schrieb L.P.H. van Belle via samba:
> I pointed to that link becuase of the last message.
>>> The OU the users were in required read permissions on the Authenticated Users security group!
> Im guyessing this is what your problem is, i just dont know where in your AD.
OK, that might be the case.
So the step is "add/check ACLs on the SYSVOL-share for
2020 Mar 05
4
DCs from 4.10.x to 4.11.x
Am 05.03.20 um 17:39 schrieb Rowland penny via samba:
> On 05/03/2020 16:31, Stefan G. Weichinger via samba wrote:
>> Am 05.03.20 um 16:09 schrieb Rowland penny via samba:
>>
>>> It took nearly 5 hours in my case and during that time, only the samba
>>> binary was running, no smbd or winbind.
>> Why 5 hours? Thousands of users?
> No, just my small test
2007 Jun 20
2
Averaging dates?
Hi,
What's the best way to average dates?
I though mean.POISXct would work fine but...
> a
[1] "2007-04-02 19:22:00 WEST"
> b
[1] "2007-03-17 16:23:00 WET"
> class(a)
[1] "POSIXt" "POSIXct"
> class(b)
[1] "POSIXt" "POSIXct"
> mean(a,b)
[1] "2007-04-02 19:22:00 WEST"
> mean(b,a)
[1] "2007-03-17
2019 Mar 13
0
replication fails
Hi Stefan,
Debian 8 ? 9?
DC's samba version ?
Can you post your smb.conf and resolv.conf
If you check with (per server what is the outcome. )
samba-tool dbcheck
samba-tool dbcheck --cross-nc
You could do a forced sync of a good server to the bad one.
https://wiki.samba.org/index.php/Manually_Replicating_Directory_Partitions
Greetz,
Louis
> -----Oorspronkelijk bericht-----
2019 Mar 13
4
replication fails
Am 13.03.19 um 18:50 schrieb Rowland Penny via samba:
> Try running 'samba-tool ldapcmp ldap://dc1 ldap://dc2'
thanks!
I get differences, too many to post here, but I assume mostly related to
the drift between the 2 dcs now?
(lastLogonTimestamp seems obvious to me)
What might solve the initial problem *maybe*
* Comparing [DNSFOREST] context...
* Objects to be compared: 19
2019 Jul 31
3
GPO issues - getting SYSVOL cleaned up again
Hai,
And thanks for the other check i needed to know if the A record did exist.
>> ldap1 CNAME pre01svdeb02
>> ldap2 CNAME pre01svdeb03
>sorry, typo -------------^
Yes i was expecting that. ;-)
What i see, all SOA record and serialnr are same where is should be so thats ok.
What i noticed is this part.
dig a dc.pilsbacher.at @192.168.16.205/206 replies.
DNS1 ( DC1
2019 Mar 13
2
replication fails
Am 13.03.19 um 17:13 schrieb Stefan G. Weichinger via samba:
> Am 13.03.19 um 16:53 schrieb L.P.H. van Belle:
>> Ok thats small, a dc should be rebooted within 1-2 min and 1-2 min really max for AD sync.
one more observation:
manually running this works:
root at pre01svdeb03:~# samba-tool drs replicate dc PRE01SVDEB03
dc=blabla,dc=at --full-sync
but the one user I created (and
2019 Jul 02
2
GPO infrastructure? -> 4.8.x to 4.9.x
I get problems with group policies not applied ... seems an older
problem surfacing now.
Before I debug at current level I consider upgrading the 2 DCs from
4.8.12 (Debian Stretch) to 4.9.9
Anything specific to consider here?
2017 Oct 10
2
samba getting stuck, highwatermark replication issue?
Hi James,
Thanks for the quick reply.
On 10/09/2017 08:52 PM, lingpanda101 via samba wrote:
> You should be able to fix the 'replPropertyMetaData' errors with;
>
> samba-tool dbcheck --cross-ncs --fix --yes
> 'fix_replmetadata_unsorted_attid'
Yep, worked great! Fixed all of those replPropertyMetaData errors! :-)
> The highwatermark doesn't necessarily
2015 Mar 27
2
Replication error after trying to sync sysvol
I tried to synchronize the sysvol folders, on two dcs. Something went
wrong since yesterday we have replication problems:
One machine shows this, while the other one is happy.
samba-tool drs showrepl
==== INBOUND NEIGHBORS ====
DC=DomainDnsZones,DC=ourdomain,DC=com
Default-First-Site-Name\DC03 via RPC
DSA object GUID: af610e1a-9e3b-4cdd-a36b-c296d77a9479
Last attempt @