similar to: SRV records not added by subsequent DC's

On Tue, 24 Jul 2018 15:00:27 +0200 Henry Jensen via samba <samba at lists.samba.org> wrote: > Hello, > > sorry to ask this many questions, but I want to know why things happen > they way they do and if perhaps something is wrong. > > Our new, shiny domain created by classicupgrade consists of 4 (four) > domain controllers. > > dc1 was the first, which was

On Tue, 24 Jul 2018 14:15:04 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 24 Jul 2018 15:00:27 +0200 > > dc1 and dc2 have created SRV DNS records: > > > > # host -t SRV _ldap._tcp.dc._msdcs.iww.lan > > _ldap._tcp.dc._msdcs.iww.lan has SRV record 0 100 389 dc1.iww.lan. > > _ldap._tcp.dc._msdcs.iww.lan has SRV record 0 100 389

On Mon, 23 Jul 2018 13:12:42 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Mon, 23 Jul 2018 14:02:45 +0200 > Henry Jensen via samba <samba at lists.samba.org> wrote: > > > > Yes, the objects in question are displayed, one of them looks like > > this: > > > > # record 46 > > dn: > >

On Mon, 23 Jul 2018 11:27:38 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > How are you searching and what with ? I used the ADUC tool and LDAPAdmin. > > Have you tried ldbedit ? > > ldbedit -e <your favourite editor> -H /path/to/sam.ldb > > This will display everything in the editor and you can then search in > that for the groups. You

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I just set up a Domain with two DCs. I use Debian jessie the debian-pakages. And bind9 also from the debian repositories. After setting up the first DC everything was working fine. The nameresolution of hosts ans SRV-records worked. Then I set up a second DC also everything aut of the debian-box with bind9 as nameserver. The

Hello, after migration from a NT style domain to Samba AD (running 4.7.8) with the classicupgrade method I have two group objects in the AD tree with german umlauts which I can't access or delete. When I try I get a error which says literally "object not found on the server". Same when using other LDAP tools. It's not a great problem, but how can I get rid of this two group

"--seize" helped: root at pre01svdeb03:~# samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at InfrastructureMasterRole owner: CN=NTDS Settings,CN=PRE01SVDEB03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=pilsbacher,DC=at RidAllocationMasterRole owner:

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan G. Weichinger via samba > Verzonden: vrijdag 12 juli 2019 10:24 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO infrastructure? -> 4.8.x to 4.9.x > > Am 10.07.19 um 08:40 schrieb Stefan G. Weichinger via samba: > > > more of this: > >

On 31/07/2019 12:04, Stefan G. Weichinger via samba wrote: > Am 31.07.19 um 12:50 schrieb Rowland penny via samba: >> On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote: >>> Am 31.07.19 um 12:32 schrieb Rowland penny via samba: >>>> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: >>>>> "dc" was the old name a few years ago

On 10/12/15 14:00, Ole Traupe wrote: > > > Am 10.12.2015 um 14:38 schrieb Rowland penny: >> On 10/12/15 13:25, Ole Traupe wrote: >>> Is it possible that kdc server is always the SOA, at least if >>> derived from DNS and not specified *explicitly* in the krb5.conf? >>> >>> In my DNS-Manager console I find that >>> >>>

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

On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN

I installed a third DC today. Replication works find, but as systemctl status samba-ad-dc showed an error w.r.t. dnsupdate I was running samba_dnsupdate ?verbose. Below is the output. It looks like there are some missing DNS records, but what are potential causes of this error: dns_tkey_gssnegotiate: TKEY is unacceptable I already checked what?s listed @

Am 04.01.2024 um 13:28 schrieb lists--- via samba: > Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >> On Thu, 4 Jan 2024 12:12:57 +0100 >> lists--- via samba <samba at lists.samba.org> wrote: >> >>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba: >>>> On Thu, 4 Jan 2024 11:19:17 +0100 >>>> lists--- via samba <samba at

Hello! I've followed your tutorial to change the IP Address of our Samba AD DC: https://wiki.samba.org/index.php/Changing_the_IP_Address_of_a_Samba_AD_DC But the samba_dnsupdate tool always crashes with this output: samba_dnsupdate --verbose Unknown parameter encountered: "ks" Ignoring unknown parameter "ks" IPs: ['192.168.68.201'] Looking for DNS entry A

Good morning :) Am 04.01.2024 um 20:17 schrieb lists--- via samba: > Am 04.01.2024 um 13:28 schrieb lists--- via samba: >> Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >>> On Thu, 4 Jan 2024 12:12:57 +0100 >>> lists--- via samba <samba at lists.samba.org> wrote: >>> >>>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba:

Hello List, I am trying to compile and install Samba 4 using the wiki guide on Centos 6.2. I am currently using the current source from git. It seems that the zone file used for Bind is not configured and not installed in the private directory. Is there any way to get this file generated so I can finish my install? Thank you for your time and have a great day!! Kind regards, Jeremy

> So you never read this: > https://wiki.samba.org/index.php/Changing_the_DNS_Back_End_of_a_Samba_AD_DC > Which means that you probably never ran the aptly named > 'samba_upgradedns'Of course I ran this. Many times. I'm not stupid, Rowland. At least I can read:D If I've seen that Bind doesn't work, I had to change backend to internal DNS.I carefully read and made

Hi, The smb.conf is the default after the upgrade: cat /etc/samba/smb.conf # Global parameters [global] workgroup = TTU realm = ttu.red netbios name = PDC interfaces = lo, eth0 bind interfaces only = Yes server role = active directory domain controller server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbind, ntp_signd, kcc,

Hello, this is a Samba AD Domain upgraded from Samba 3.x with classicupgrade. Debian 9.4 Samba: 4.7.6 (packages from tranquil.it) # cat /etc/samba/smb.conf [global] netbios name = DC1 realm = IWW.LAN server role = active directory domain controller workgroup = IWW idmap_ldb:use rfc2307 = yes dns forwarder = 172.16.1.12 dsdb:schema update