Displaying 20 results from an estimated 3000 matches similar to: "Replication and KCC problems on upgrade"
2019 Mar 01
0
Replication and KCC problems on upgrade
On Thu, 28 Feb 2019 18:04:50 -0600 (CST)
Mike Ray via samba <samba at lists.samba.org> wrote:
> Hello all-
>
> I am trying to upgrade a old domain to a newer version. The old DCs
> are a custom compiled version of Samba, so instead of upgrading the
> DCs in place, the plan is to upgrade by joining new DCs to the
> domain, replicating data and then shutting down the old
2019 Mar 01
2
Replication and KCC problems on upgrade
----- On Mar 1, 2019, at 3:35 AM, samba samba at lists.samba.org wrote:
>
> I wonder if this has anything to do with the 'you cannot upgrade
> directly from 4.7.x to 4.9.x' bug ?
I was not aware of this bug. Do you think I should scrap this upgrade and try again jumping like so? 4.0.6-12 -> 4.7 -> 4.8 -> 4.9
> I know this might seem strange, but try running
2023 Apr 03
1
WARNING: no target object found for GUID component link lastKnownParent in deleted object
hi,
I have this DC in aws to fulfill the authentication need of our moodle.
# samba -V
Version 4.17.7-Debian
DNS with SAMBA_INTERNAL
The replication of the users and groups happens correctly. Some errors in
running samba_dnsupdate, but it is ok anyway.
When I ran the command samba-tool dbcheck, I got the return below.
# samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes
2023 Apr 04
1
WARNING: no target object found for GUID component link lastKnownParent in deleted object
While this should work, neither is this particularly harmful. ?Links to
objects that don't exist are ignored at runtime.
Andrew Bartlett
On Tue, 2023-04-04 at 14:39 -0300, Elias Pereira via samba wrote:
> hi,
>
> Any clue?
>
> On Mon, Apr 3, 2023 at 10:17?AM Elias Pereira <empbilly at gmail.com> wrote:
>
> > hi,
> >
> > I have this DC in aws to
2018 Jan 31
2
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
Hi Stefan
I am also one of the Sernet customer. Can you guide me how to run the patch
to fix the bug.
I am running 2 DC's Sernet Samba 4.7.4 with 2 RODC's running Sernet Samba
4.7.4. Whenever I run samba-tool drs replicate --fix --yes command on the
DC it shows the below errors which cannot be fixed:
Failed to remove deleted DN attribute fromServer : (65, "objectclass_attrs:
at
2018 Jan 22
6
[Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228)
Hi,
here're patches to avoid a database corruption with linked attributes,
e.g. member/memberOf.
See https://bugzilla.samba.org/show_bug.cgi?id=13228
As a temporary solution admins can add "server services = -kcc" to the
global section of smb.conf.
Also DO NOT repair the following errors with samba-tool dbcheck!
"Remove duplicate links in attribute"
and
"ERROR:
2017 Oct 05
2
Magically disappearing errors during FSMO transfer
Recently tried transferring roles from Samba 4.3.11 to Samba 4.7.0. Ultimately,
both dcs agreed that the 4.7.0 dc (dc3) had all the roles and replication and
the databases were in good shape. However, during the process, I got a lot of
errors that seemed to magically disappear.
Should I be worried?
root at dc3:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS
2024 Sep 24
1
dbcheck and fix
Hi all!
I demoted a samba 4.10.8 (slackware 14.2) ad dc called DC1 and joined to the domain a samba 4.20.4 (debian 12.7) called DC3. There is also a samba 4.18.9 (slackware 15.0) ad dc called DC2 which for the moment holds all the FSMO roles. The whole replacing an ad dc with another one worked out great but when I run the command samba-tool dbcheck --cross-ncs on DC2 I got 3 "NOTES"
2024 Oct 04
1
dbcheck and fix
?On 2/10/2024, 3:43 PM, "samba on behalf of bd730c5053df9efb via samba" <samba-bounces at lists.samba.org <mailto:samba-bounces at lists.samba.org> on behalf of samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote:
On Tuesday, September 24th, 2024 at 15:29, bd730c5053df9efb via samba <samba at lists.samba.org <mailto:samba at lists.samba.org>>
2019 Jan 22
2
dbtool --cross-ncs and undeletable errors..
On Tue, 22 Jan 2019, Rowland Penny via samba wrote:
> On Tue, 22 Jan 2019 14:20:21 -0500 (EST)
> "Vincent S. Cojot via samba" <samba at lists.samba.org> wrote:
>
>>
>> Hi All,
>>
>> On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02
>> and 03 are gone), I've noticed the following errors which I am unable
>> to
2019 Jan 22
2
dbtool --cross-ncs and undeletable errors..
Hi All,
On my two-DC setup (dc00 and dc01 - Used to be a 4-Dc setup but 02 and 03
are gone), I've noticed the following errors which I am unable to fix.. Any hints?
* Basic dbcheck is clean.
[root at dc00 ~]# samba-tool dbcheck
Checking 327 objects
Checked 327 objects (0 errors)
* Cross-NCS shows two errors related to a de-comissionned DC (dc02) and
cannot auto-fix this.. How do I fix
2018 Mar 28
1
The 'not-always-on' infrastructure at home and Samba4 AD DC's..
Hi everyone,
Apologies in advance, this will be a bit long but I'm hoping to get some
guidance and hints on usual practices for using Samba4 AD DC as an Idm for
W10 laptops that might be on the road elsewhere..
As much as I have been using samba for file serving, a Samba AD DC is
something new to me.
I built a small Samba AD DC infrastructure to serve UIDs and Passwords (4
VMs on 4 KVM
2018 May 17
3
Dcs Replication
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
2013 Apr 29
1
Global Catalog replication error to win 2008
Hi all,
Running Samba 4.0.0apha18 with good results but getting an error when I attempt to replicate the Global Catalog to a Windows 2008 Machine.
Samba machine = DC1
Windows 2008 machine = DC0
samba-tool Showrepl result:
Default-First-Site-Name\DC1
DSA Options: 0x00000001
DSA object GUID: 05c3c860-0a0d-4672-a39e-a212ccb0ce9c
DSA invocationId: abb0cab3-13d3-456c-8a16-e65a4855a2df
==== INBOUND
2016 Mar 27
2
Unable to join DC to domain
I ran ldbsearch on my sam.ldb
I searched for CBADC02, CBADC03, and TESTES (all VMs that fail to join
domain), results are below:
CBADC02 shows up a few times:
# record 1906
dn:
CN=CBADC02\0ADEL:de85228c-f92b-4d5d-9d6a-01c3f915dec9,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configu$
objectClass: top
objectClass: server
instanceType: 4
whenCreated: 20160310044543.0Z
uSNCreated: 4215
2017 Jul 11
2
Samba ADS-member-server: FQDNs in /etc/hosts
Am 2017-07-11 um 14:57 schrieb Rowland Penny:
>> # smbclient \\\\server\\daten -Usgw%PW
>> session setup failed: NT_STATUS_UNSUCCESSFUL
>
> Restart all the Samba binaries on the DM
>
> Then check that the OS knows your user with:
>
> getent passwd sgw
libnss_winbind was missing!
Now both results are the same
user-names in /etc/passwd ... rmed now
I was 100%
2016 Mar 28
2
Unable to join DC to domain
Alright... appreciate the info. Gave it a shot. Domain is still up but
shares are down because they were hosted on FILER which has now been
demoted and is no longer running any samba services.
What I did while following the wiki "Transfer/Seize FSMO Roles":
1) logged on to FILER, ran samba-tool fsmo show, verified all 7 roles were
owned by FILER.
2) logged on to CBADC01, executed
2020 Feb 27
3
User names not replicating to secondary DC
> > DC1 smb.conf
> > winbind use default domain = true
> > winbind offline logon = false
> > winbind nss info = rfc2307
> > winbind enum users = yes
> > winbind enum groups = yes
>
> The above lines have no place in a DC smb.conf or are defaults
Commented them out.
>
> Change the following files as shown:
2017 Sep 29
2
Replication Error Between Differing Samba Versions During Upgrade
Hey all-
Trying to upgrade the domain and running into issues getting my data into the
new controller.
Current configuration:
dc0 - Ubuntu 12.04.2 - Samba: 2:4.0.6-12
dc1 - Ubuntu 12.04.2 - Samba: 2:4.0.6-8
dc2 - Ubuntu 12.04.3 - Samba: 2:4.0.6-8
I'm trying upgrade to Ubuntu 16.04.3, Samba: 2:4.3.11+dfsg-0ubuntu0.16.04.10
The documentation
2019 Mar 25
2
samba 4.9.5 - joining Samba DC to existing Samba AD failed
Dne 2019-03-25 16:02, Rowland Penny via samba napsal:
> On Mon, 25 Mar 2019 15:12:16 +0100
> franta via samba <samba at lists.samba.org> wrote:
>
>> Hi team,
>> I have Samba (4.9.5) AD DC, and when trying to add second DC, join
>> fail:
>>
>> # samba-tool domain join zamecek.home DC
>> -U"SSUPS-ZAMECEK\administrator"