similar to: 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

----- 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

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

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

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

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

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:

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

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

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"

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

On Thu, 5 Oct 2017 14:14:56 -0500 (CDT) Mike Ray via samba <samba at lists.samba.org> wrote: > 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 >

?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>>

On 20/09/2020 00:30, Elias Pereira via samba wrote: > hi, > > I listed the 0ADEL entries with the command below and didn't find the > object. > # ldbsearch --cross-ncs --show-deleted -H /var/lib/samba/private/sam.ldb | > grep "\0ADEL" > > I tried to delete using the command below, but it says it doesn't exist. > # ldbdel -H

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

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

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

> > *named.conf.options* > > options { > > directory "/var/cache/bind"; > > > > // If there is a firewall between you and nameservers you want > > // to talk to, you may need to fix the firewall to allow multiple > > // ports to talk. See http://www.kb.cert.org/vuls/id/800113 > > > > // If

I have hollowed these instructions. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt My normal domain is company.com. For the Samba domain it is msi.company.com. DNS is working. I ran these commands. host -t SRV _ldap._tcp.msi.company.com. _ldap._tcp.msi.company.com has SRV record 0 100 389 dc0.msi.company.com. host -t SRV _kerberos._udp.msi.company.com.

On 24/07/2019 17:05, Rowland penny via samba wrote: > On 24/07/2019 16:01, Carlos via samba wrote: >> Hi >> >> samba-tool dbcheck >> ERROR(<class 'KeyError'>): uncaught exception - 'No such element' >> ? File >> "/opt/samba/lib/python3.6/site-packages/samba/netcmd/__init__.py", >> line 185, in _run >> ??? return