similar to: SPN and case sensitivity on LMDB backend

directory service replication does not work between windows DC and samba DC, as the samba DC has 2 identical WSMAN records samba-tool  spn list m7-arhiv$ m7-arhiv$ User CN=M7-ARHIV,OU=Computers M07,DC=example,DC=ru has the following servicePrincipalName:      HOST/M7-ARHIV      HOST/m7-arhiv.example.ru      RestrictedKrbHost/M7-ARHIV      RestrictedKrbHost/m7-arhiv.example.ru    

Hi Rowland, On Tue, 7 Aug 2018 09:46:24 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: > > spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] > > account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] > > forest[mydom.lan] domain[mydom.lan] > > > > At

On Tue, 7 Aug 2018 12:51:33 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: > > > > spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] > > > > account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] > > > > forest[mydom.lan] domain[mydom.lan]

Hello, I've got some log entries like these on our DCs: Failed to modify SPNs on CN=db1,CN=Computers,DC=mydom,DC=lan: acl: spn validation failed for spn[TERMSRV/DB1.MYDOM] uac[0x1000] account[db1$] hostname[(null)] nbname[mydom] ntds[(null)] forest[mydom.lan] domain[mydom.lan] At first I thought it was about missing SPN entries, but adding these did not resolve the problem: # samba-tool

On Tue, 7 Aug 2018 14:59:56 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 7 Aug 2018 14:55:24 +0200 > Henry Jensen via samba <samba at lists.samba.org> wrote: > > > On Tue, 7 Aug 2018 12:51:33 +0100 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > > > > Failed to modify SPNs on

Hi all, SPN = servicePrincipalName A simple search returning all servicePrincipalName declared in your AD: ldbsearch -H $sam serviceprincipalname=* serviceprincipalname An extract from result concerning a lambda client: # record 41 dn: CN=win-client345,OU=Machines,DC=ad,DC=domain,DC=tld servicePrincipalName: HOST/MB38W746-0009 servicePrincipalName: HOST/MB38W746-0009.ad.domain.tld

On Fri, 23 Oct 2020, Rowland penny via samba wrote: > On 23/10/2020 15:03, Tom Diehl via samba wrote: >> Hi, >> >> I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. >> I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to >> 4.12r.latest. >> >> In doing this I ran samba-tool dbcheck --reindex and got

On Tue, 7 Aug 2018 16:26:36 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Tue, 7 Aug 2018 17:13:02 +0200 > Henry Jensen via samba <samba at lists.samba.org> wrote: > > > On Tue, 7 Aug 2018 14:59:56 +0100 > > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > On Tue, 7 Aug 2018 14:55:24 +0200 >

Hi, I have 2 DC's. One is running 4.10.18 and the other is running 4.11.14. I am planning on upgrading the 4.10.18 DC to 4.11.14 and then both up to 4.12r.latest. In doing this I ran samba-tool dbcheck --reindex and got the following warning: (vdc1 pts8) # samba-tool dbcheck --reindex Re-indexing... ../../lib/ldb/ldb_key_value/ldb_kv_index.c:2413: duplicate attribute value in

Just a though as I was passing in the neighbourhood: does your Terminal Server have related SPN (ServicePrincipalName) created on computer objects? servicePrincipalName: HOST/W7AD-02 servicePrincipalName: HOST/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02 HOST/<hostname> should exist on all computers, that's just to be

On Tue, 2023-04-04 at 09:37 +0200, Kees van Vloten wrote: > Op 04-04-2023 om 00:32 schreef Andrew Bartlett: > > > > > On Mon, 2023-04-03 at 15:08 +0000, Tim ODriscoll via samba wrote: > > > > > Unfortunately it's still erroring out: > > > (7) mschap: Creating challenge hash with username: host/SL-6S4BBS3.MYDOMAIN.co.uk > > > (7) mschap:

Hi, In samba role DC, is the issue of duplicate SPN records fixed?

Hi guys, i have some issue with our company DC (samba 4.7.12 on a Debain 9 machine) and work ok from about 3 years. Now we tried to join another DC for redundancy but we receive the following error: Provision OK for domain DN DC=example,DC=com Starting replication Schema-DN[CN=Schema,CN=Configuration,DC=example,DC=com] objects[402/1550] linked_values[0/0]

Hello, I have now spent 30 hours trying to get this working, so it's time to get some professinoal help. :) In a nutshell, I would like to have a sambda AD PDC that authenticates both Windows and Debian. On Linux, I would like to use SSSD. I have followed the steps on the wiki: - https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO -

On Mon, 20 Nov 2023 15:34:19 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote: > Full output: > > root at iob-master:~# samba-tool domain backup online --server=dc01 > --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U > administrator Password for [SAMBA\administrator]: > INFO 2023-11-20 15:30:05,639 pid:73781 >

Full output: root at iob-master:~# samba-tool domain backup online --server=dc01 --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U administrator Password for [SAMBA\administrator]: INFO 2023-11-20 15:30:05,639 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA INFO 2023-11-20 15:30:05,640 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1617: realm

Hello, I've setup over 6 months ago samba 4 AD on centos 7.3 (self compiled from source). Up until now I didn't encounter any undocumented errors. I have 3 DC's (all samba 4.5.3) which are working pretty nice with over 60 windows clients. The issue I've stumbled upon is when I added Windows server Hyper-V hosts to the domain. Tried with Hyper-V from 2012, 2012r2 and new 2016

Hi, Does anyone have experience of using ldbedit or similar, to remove the duplicates below? (Is that even the right way for me to go?) Can I perhaps query something using ldbsearch, to find the duplicates, before using ldbedit? On Sun, 18 Nov 2018 at 21:37, Jonathan Hunter <jmhunter1 at gmail.com> wrote: > [...] > In my database, as reported by the domain join command above, I have

Hi, I'm using Samba 4.10.7 with Bind9_DLZ (9.10.3-P4-Debian), but I'm not getting to insert a new DC into the Domain. Following is the command used and the error: root at samba4-dc3:/var/lib/samba/private# samba-tool domain join empresa.com.br DC -k yes --server=samba4-dc1.empresa.com.br --dns-backend=BIND9_DLZ -d 3 INFO 2019-09-02 15:50:33,684 pid:6636

OK, Thanks for all. Regards; On 23/07/2019 12:06, Rowland penny via samba wrote: > On 23/07/2019 16:02, Carlos via samba wrote: >> I haven't more output log, because i need join in dc in last week, >> and i "resolved"(workaround) in used samba 4.6.X -> after -> 4.8.3. >> Sorry..... > > OK, it would have been nice to have the output, this is