similar to: Bad zone problem after join, seize, demote

On Tue, 24 Jul 2018 09:17:41 +0300 Taner Tas via samba <samba at lists.samba.org> wrote: > I'm testing to a seamless upgrade from 4.3.11 to 4.8.3 on my test > setup. Database migrating from 4.3.11 was successful. After > "samba-tool dbdcheck --cross-ncs --fix --yes", 4.8.3 was launching ok > except replication (4.3.11 to 4.8.3 : WERR_BADFILE). After demoting >

Hi, I migrated our DCs from 4.5/internal dns to 4.7.1/bind9_dlz. Short summary of the steps taken: - added a new temp dc, - removed the old DCs - cleaned sam database - installed new DCs, with their old dns/ip - removed the temp dc again - synced sysvol and all is looking well: no db errors, no replication issues, ldapcmp matches across DCs, etc. So, I took things to production today, and

Greetings, I am in the process of replacing my MicroFocus (Novell) eDirectory system with a Samba-based Active Directory system. I've got three domain controllers built, and they seem to be humming along nicely. Server OS is Ubuntu 18.04 patched current. I started off with the Samba 4.7 packages included in the default Ubuntu repository, but have since upgraded to Samba 4.10 using packages

PRIOR THREAD: https://lists.samba.org/archive/samba/2019-January/220292.html In the  referenced prior thread, I had an issue of samba_dnsupdate --verbose --all-names causing a dns_tkey_gssnegotiate: TKEY is unacceptable error. Ultimately, the solution kindly provided by Rowland was to insert dns update command = /usr/local/samba/sbin/samba_dnsupdate --use-samba-tool into the [global] section of

Hi all, i've got initial setup on DC1 (4.0.1)... all working good and flawless Added additional geographically distributed controllers (DC2, DC3, DC4,DC5) with 4.0.5 - no problem. All PC's can connect to their own site/DC Transferred all FSMO's to DC2 - transferred successfully (with seize "error" bug) DC1 crashed badly.... during maintenance, SAMBA was

On Thursday, January 10, 2019 1:43 PM, Rowland Penny via samba <samba at lists.samba.org> wrote: >On Thu, 10 Jan 2019 19:09:01 +0000 (UTC) >Billy Bob via samba <samba at lists.samba.org> wrote: > > >> >> As to the current issue, I am attemting to configure DHCP to update >> DNS records with BIND9, as outlined in the Samba Wiki (with >>

On 21/09/2020 15:23, Elias Pereira via samba wrote: >> The question has to be, why do you only have it on one DC ? > > I am also asking myself this question because the dc3 was the first one I > provisioned. > > Ok. Somehow this was removed. Would it be possible to recreate this entry > or the best thing to do is to change the roles to dc4 and provision another > DC

Hello List, Hello Rowland :-) again I'm having problems with the DDNS. I did it as shown in the wiki. I took all teh scripts from the wiki the dhcp-dyndns.sh is Version: 0.8.9 I configured everything including the failover. When I start the two DHCP-Server everything is perfect. I see the right messages in the log, the two DHCP-Servers are talking to each other. When a Client ask for an

On 21/09/2020 15:00, Elias Pereira via samba wrote: > Another doubt is about this bydefaults entry. > The dc4 has this entry, but the dc3 does not. The dc3 is the fmso roles guy. > Does it work that way or is there something wrong there? Whilst there are a few attributes that do not replicate, all DN's should. > * Comparing [DOMAIN] context... > > * DN lists have different

Hi List, We are running through testing our migration to Samba4/AD domain and hit an odd issue. We set up one new VM as a legacy PDC and performed a migration on this machine. All went fine. We added a second DC with no issues. We then simulated the first DC going away by unplugging the VM NIC and did an FSMO seize. The next step was to reinstall the original VM from scratch as a new DC on

On Mon, 2019-04-29 at 18:56 +0100, Rowland Penny via samba wrote: >  > That shouldn't make any difference, the 2003 level only used the > three > enctypes you have now, this is on one of my DC's: > >  root at dc4:~# samba-tool domain level show > Domain and forest function level for domain > 'DC=samdom,DC=example,DC=com' > > Forest function level:

Am 21.06.2016 um 12:10 schrieb lists: > Hi Achim, list, > > On 21-6-2016 11:26, Achim Gottinger wrote: >> Exactly, rsync should map user and group names if the demon on the >> destination runs as root. But this does not work. I tested it with an >> group named test with gid 1000 on server #1 and gid 1001 on server #2. >> It works if rsync is used via ssh like this

Hi, I have three Samba Domain Controllers, two in the LAN local network (dc1 and dc2) and one in a remote network which is accessible from the LAN through a VPN connection (dc4). Every domain controller can reach every other domain controllers, and every type of traffic is permitted by firewalls, they can ping and access to every TCP and UDP ports. Checking the Samba replication I see that the

Nithya, Is there any way to increase the logging level of the brick? There is nothing obvious (to me) in the log (see below for the same time period as the latest rebalance failure). This is the only brick on that server that has disconnects like this. Steve [2017-10-17 02:22:13.453575] I [MSGID: 115029] [server-handshake.c:692:server_setvolume] 0-video-server: accepted client from

My reverse zones have PTR records. Though I don't have NS records for all of my DC's. I guess that needs to be manually created. Also, you don't have any CNAMES or domain overrides pointing to a single DC? Perhaps Bind is pointing to another internal DNS server, and then to a public DNS? ---- Here's a way to test failover from a Windows client: You can switch logon servers

> Hi all, > > We have a Samba AD DC service running on Ubuntu 16.0.4 with Samba > 4.3.11. We are planning to upgrade it to a recent version, probably > 4.8.3. > > I think that I have two options: > > a) Package upgrade via 3rd party repositories (Louis Van Belle's repo) > by following wiki. > > b) A fresh install of 4.8.3 on another VM then join it to

Hi, After joining samba DC (vm-dc4) to MS AD, I've discovered that most DNS entries were not populated. Below are the only entries in the AD for the new DC: domain.com:VM-DC4 900 A 172.26.1.84 _msdcs.domain.com:d14c4206-79e3-441f-868a-6c693415256a 900 CNAME vm-dc4.domain.com. Please, help me figure out what's going on. Here is the excerpt from log.samba:

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

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

About a week and half ago I upgraded from 4.0.12 to 4.9.6. Overall, things are functioning. However, I have come across several strange behaviors and wandered if anyone else has noticed similar behavior on 4.9.6 or has any suggestions of what might be occurring. As background information, I have 3 DCs (dc3, dc4 and dc5) -- all running the same version (4.9.6) and all have the same configuration;