similar to: after DCs migration to 4.7, two things

Hi Marc, Thanks for your reply! > Check if your dynamic DNS works. For details and troubleshooting, see: > https://wiki.samba.org/index.php/Testing_Dynamic_DNS_Updates I'm not sure about the "--all-names" option, but the regular "samba_dnsupdate --verbose" updated all dns records for all DCs shortly after I joined them. The problematic dns records here are

On Tue, 7 Nov 2017 21:07:21 +0100 lists via samba <samba at lists.samba.org> wrote: > Hi Marc, > > Thanks for your reply! > > > Check if your dynamic DNS works. For details and troubleshooting, > > see: https://wiki.samba.org/index.php/Testing_Dynamic_DNS_Updates > > I'm not sure about the "--all-names" option, but the regular >

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 older ones and seize (transfer doesn't work) all roles to 4.8.3, dns (bind_dlz) service won't start anymore

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;

On 12/02/2020 12:54, L.P.H. van Belle via samba wrote: > > >> Hello Louis, >> >> Thanks for your reply. >> >> For that dig command I get... >> >> >> root at dc3.mydomain.com ~ $ (screen) dig NS $(hostname -d) >> >> ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS mydomain.com >> ;; global options: +cmd

im on phone, had a quick small look at the dc3 output. is your time in sync, it looks like a 3 - 10 min different. gr. Louis Op 7 mei 2019, om 18:34, Elias Pereira <empbilly at gmail.com> schreef: Hello, dc3: http://pasted.co/6b703479 dc4: http://pasted.co/5068fc6e diff: http://pasted.co/025c3242 On Tue, May 7, 2019 at 12:08 PM L.P.H. van Belle via samba <samba at

Hello, I had posted this in another topic, but because the problem is different, I decided to create a new topic. Conf: - Primary DC/pdc Emulator as DC3 - Second DC as DC4 After an upgrade from schema 45 to 69 in DCs, when adding a computer in the domain and if the domain to respond is DC4 the synchronization for DC3 is not done. I already did several tests that I already knew and also new

On Thu, 17 May 2018 17:19:17 -0300 Carlos via samba <samba at lists.samba.org> wrote: > I understand, but dont replication between sites, is my problem.... > > Regards; > Lets start by confirming if this is your setup: Matriz site Filail DC1 --------------- DC3 | | | | DC2

On 13/02/2020 16:28, Paul Littlefield wrote: > On 13/02/2020 15:17, Rowland penny via samba wrote: >> The various ways have already been mentioned, but are all your DCs >> listed as nameservers (NS) in the SOA's for the forward and reverse >> zones ? > > > I think so... > > > root at dc3.mydomain.com ~ $ (screen) samba-tool dns query dc3 >

On 03/02/2020 18:49, Kris Lou via samba wrote: > > From windows: > echo %logonserver% \\DC3 > nltest /dsgetdc:<domain> DC:\\DC3 Address: \\192.168.0.218 Dom Guid: bla bla bla ... The command completed successfully. > From a *nix domain member (i.e. client, not DC): > wbinfo --getdcname=<domain> > winbind --ping-dc wbinfo --getdcname=MYDOMAIN DC3 wbinfo

Hai,   Now, differences is fine, but can you see if one of the 2 servers is correct, and for that it might be handy to share the output.   You can push the good DB to the other DC. ( a forced replication )   And i can understand why you upgrade ...  Did you see :    samba-tool domain schemaupgrade --help Usage: samba-tool domain schemaupgrade [options] Domain schema upgrading Options:   -h,

Hello Kris, On 03/02/2020 07:15, Kris Lou via samba wrote: > Unless it's_not_ a global catalog. Check your SRV records again, there > should be corresponding "_gc" records (similar to "_ldap") for each DC. Checked and both DCs pass all tests:- host -t SRV _ldap._tcp.mydomain.com. host -t SRV _gc._tcp.mydomain.com. host -t SRV _kerberos._udp.mydomain.com. host -t

Hi, Searching my samba logs for errors, I noticed the following logged occasionally on (all three) DCs: > ../../librpc/rpc/dcerpc_util.c:373: ERROR: pad length mismatch. Calculated 44 got 0 Searching the samba archives, they seem to be related to DNS. So I checked our config. We're on buster, with: > root at dc2:~# dpkg -l | grep bind9 > ii bind9

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 13/02/2020 13:11, Paul Littlefield wrote: > On 12/02/2020 13:08, Rowland penny via samba wrote: >> The first is that a DC must use itself as its nameserver and if >> something goes wrong e.g. Samba has fallen over, then there isn't >> much point having another nameserver, Samba isn't going to use it >> >> The second is, it will not hurt having a second

Hi, Again more data: The command samba-tool visualize reps seems to agree with the observed lack of replication from DC4 to DC3 & DC2: > RepsTo objects for DOMAIN > destination >

Hello, dc3 = principal DC dc4 = secondary DC I had this problem last month after updating samba to version 4.10.x. and also the schema from 45 to 69. But it looked like it had been corrected. Today I noticed that on dc4 there are computers that are not on dc3. I updated: 4.7.x to 4.8.x 4.8.x to 4.9.x and only after that I upgrade to 4.10.x version. When I run these commands: samba-tool

a quick read and one thing, the dc4, after the upgrade to 4.7, did you reindex the ad database? if im correct, samba-tool dbcheck — reindex i did read that from a list somewere, a responce of andrew. greetz Louis (mobile) Op 23 okt. 2017 om 20:47 heeft mj via samba <samba at lists.samba.org> het volgende geschreven: Hi, Back in the samba 4.1 days, we experienced a samba database

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

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