Displaying 20 results from an estimated 4000 matches similar to: "Error when joining new DC"
2024 Dec 07
2
Error when joining new DC
On Sat, 7 Dec 2024 12:56:08 +0000
Peter Mittermayer via samba <samba at lists.samba.org> wrote:
>
> Hi,
>
> I'm trying to upgrade my very old samba domain controllers (4.11) to
> latest samba. (4.21). The process I'm following is to demote on of
> the existing DCs and repalce it with a news system (up-to-date OS &
> samba version). Unfortunately when
2024 Dec 07
1
Error when joining new DC
Hi,
I'm trying to upgrade my very old samba domain controllers (4.11) to latest samba. (4.21). The process I'm following is to demote on of the existing DCs and repalce it with a news system (up-to-date OS & samba version). Unfortunately when trying to join as DC I get below error:
INFO 2024-12-05 19:29:42,222 pid:126140 /usr/local/samba/lib64/python3.9/site-packages/samba/join.py
2024 Dec 11
1
Error when joining new DC
On Wed, 11 Dec 2024 16:46:37 +0000
Peter Mittermayer via samba <samba at lists.samba.org> wrote:
> Hi,
> To rule out any issues with cryptographic libraries I have tried to
> join only after setting 'update-crypto-policies --set
> DEFAULT:AD-SUPPORT-LEGACY' and as this did not make a difference
> 'update-crypto-policies --set LEGACY' each followed by a reboot.
2020 Feb 10
4
FW: samba_kcc issue after joining the domain as a DC
Hai,
Ok. I did more digging, this is a link Dennis showed which might help..
https://www.itprotoday.com/windows-78/q-how-can-i-create-domaindnszones-directory-partition
Now, if i go throught the mailing list and lookup everything abotu this part.
> Could not find machine account in secrets database: Failed to fetch
> machine account password for DOM from both secrets.ldb (Could not
2020 Feb 19
3
Disk faillure on DC
Hi all, again, I ask for your help.
I have a domain with 2DC's running samba 4.10.6. The disk on the DC holding
the FSMO's failed. I recovered most of it from backups, and reinstalled
samba hopping to rejoin it to the domain.
However, when I try
# kinit administrator
#samba-tool domain join eurohidra.local DC -Uadministrator
I get
#Could not find machine account in secrets database: Failed
2020 Jul 08
6
How to delete an unwanted NS record
On Wed, July 8, 2020 04:23, Rowland penny wrote:
> On 08/07/2020 08:50, Mani Wieser via samba wrote:
>>
>> On 07.07.2020 22:14, Mani Wieser via samba wrote:
>> Found it (while having my morning walk with the dog): same as with
>> SOA: this is a zone/domain thing and not record
>>
>> Usage: samba-tool dns delete <server> <zone> <name>
2019 Jul 17
3
Can't find machine account
On 07/17/2019 12:48 PM, Rowland penny via samba wrote:
>
> What are you trying to join to ?
Active Directory domain, the only DC is a Server 2003 machine.
>
> Have you removed any existing smb.conf file ?
Yes
>
> Can you post the contents of the following files:
>
> /etc/hostname
athena
>
> /etc/hosts
127.0.0.1?????? localhost?????? localhost.localdomain
2019 Jul 17
2
Can't find machine account
I'm trying to join as a DC using Debian Buster and samba package
(v4.9.5) and I'm getting this error when I attempt to join:
> Could not find machine account in secrets database: Failed to fetch
> machine account password for DOM from both secrets.ldb (Could not find
> entry to match filter: '(&(flatname=DOM)(objectclass=primaryDomain))'
> base: 'cn=Primary
2018 Mar 02
3
Error joining Samba 4.7.4 DC to existing Win2008R2 domain
Thanks for your attention
> You are always receiving these:
>
> Adding DNS A record SRVAD-NEW.SAMDOM.LOCAL for IPv4 IP: 10.0.3.100
> Join failed - cleaning up
Yes, but the DNS record is created and it persists after the failure.
Another thing I've noticed using RSAT "Active Directory Users and
Computers" is that the new DC computer account SRVAD-NEW$@SAMDOM.LOCAL
is
2018 Mar 02
2
Error joining Samba 4.7.4 DC to existing Win2008R2 domain
> Garming asked you to see if you could locate
> where the records got put the records by hand
Sorry, I can't understand what you mean with "if you could locate where
the records got put"...
Are you're asking me to create the DNS record by hand with RSAT on
SRVAD_OLD, then run samba-tool join again?
If so, yes I've tried to create the record manually and re-run
2020 Feb 10
3
FW: samba_kcc issue after joining the domain as a DC
Guys,
> On 10/02/2020 14:40, L.P.H. van Belle via samba wrote:
>> @Rowland.
>>
>> I now see he only mailed me.
>> Here you go..
> No, he emailed me as well, but I missed this:
> samba-tool domain join domain.com DC -k yes --dns-backend NONE
> --server=vm-dc1.domain.com
> Why did he do that ? why no dns server ?????
This is b/c we used to host AD zone on
2019 Jul 18
1
Can't add DNS records when joining Windows DC (Was Can't find machine account)
On 18/07/19 7:12 AM, Rowland penny via samba wrote:
> On 17/07/2019 19:31, Robert A Wooldridge via samba wrote:
>>
>> Here's the full error:
>>
>> Could not find machine account in secrets database: Failed to fetch
>> machine account password for EDM from both secrets.ldb (Could not
>> find entry to match filter:
>>
2024 Jul 17
1
dbcheck gets uncaught exception
>> The only additional output I get from running with debug
>>
>> samba-tool dbcheck --cross-ncs --fix -d 10
>>
>> is
>>
>> ndr_pull_dom_sid: ndr_pull_error(Range Error): value out of range at
>> ../../librpc/ndr/ndr_sec_helper.c:329
OK I think I'm at least a small step further.
I realized that tdbbackup failed on
2018 Nov 29
4
Setup a Samba AD DC as an additional DC
Hai Barry,
> Onderwerp: [Samba] Setup a Samba AD DC as an additional DC
>
> >What is the running AD DC its os version/build, it was an MS server?
> 2 AD DCs Windows 2012, 1 is 2008, but the DC for the join is
> a 2012 windows DC
Yes, but win 2012 which one? 2012 or 2012R2
Can you open a dosbox (cmd) and type : ver
The build nummer is?
>
> Then question after
2019 Jul 18
2
Can't find machine account
On 07/17/2019 02:12 PM, Rowland penny via samba wrote:
> On 17/07/2019 19:31, Robert A Wooldridge via samba wrote:
>> Active Directory domain, the only DC is a Server 2003 machine.
> Is the function level set to its highest level ?
Apparently not.? It is set to Windows 2000 level.? It could be set to
Server2003 level but it thinks that one of my file servers is a domain
controller
2018 May 11
2
smb_krb5_open_keytab failed (Key table name malformed)
Hi.
I joined a fileserver system with Samba version 4.5.12-Debian (fileserv) in
an Active Directory domain managed by a Samba 4.6.7-Ubuntu installed on
another system using "realm discover" and sssd.
The Samba fileserver is correctly joined into the domain and I can
correctly browse AD users:
root at fileserv:/# getent passwd my.user
2018 Nov 27
10
Setup a Samba AD DC as an additional DC
Hai,
I had a quick look.
Barry, can you get this script and run it.
https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh
Then post the results to the list.
It collects all info i need to have a better look.
I have a few ideas, this might be a resolving order problem, i've based on the errors below.
Can you also post the output of bind from the point its
2024 Dec 11
1
Error when joining new DC
The new DC is using fixed IP and two other DCs are configured as nameserver in resolv.conf.
This is the krb5.conf:
[libdefaults]
default_realm = SUB.DOM.TLD
dns_lookup_realm = false
dns_lookup_kdc = true
________________________________________
From: samba <samba-bounces at lists.samba.org> on behalf of Rowland Penny via samba <samba at lists.samba.org>
Sent:
2024 Dec 11
1
Error when joining new DC
On Wed, 11 Dec 2024 17:26:48 +0000
Peter Mittermayer <samba.lists at outlook.com> wrote:
> OS is RHEL9.4. But I see exactly the same when trying with RHEL8.
>
First, you do not need to build Samba yourself, you can get it from
Tranquil IT.
Please post your /etc/krb5.conf file
I take it that new DC is using a fixed IP and is also using another DC
as its first nameserver before the
2024 Dec 11
1
Error when joining new DC
On Wed, 11 Dec 2024 18:28:25 +0000
Peter Mittermayer <samba.lists at outlook.com> wrote:
> The new DC is using fixed IP and two other DCs are configured as
> nameserver in resolv.conf.
>
> This is the krb5.conf:
> [libdefaults]
> default_realm = SUB.DOM.TLD
> dns_lookup_realm = false
> dns_lookup_kdc = true
>
Nothing wrong there.