Displaying 20 results from an estimated 2000 matches similar to: "Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC"
2018 Mar 14
2
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
This showed up at -d3:
DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is
CN=foo,OU=bar,DC=baz
Failed to apply records: Failed to locally apply remote add of
CN=foo,OU=bar,DC=baz: ../lib/ldb/ldb_tdb/ldb_index.c:2012: Failed to
re-index servicePrincipalName in CN=blah,OU=blah,DC=blah - (null):
Operations error
Failed to commit objects: WERR_GEN_FAILURE
I've deleted the object
2018 Mar 14
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
Note that I turned up to -d5 but the relevant output didn't seem to
change. I just cleaned up my obfuscation for clarity (all referenced DNs
were identical):
DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is
CN=foo,OU=bar,DC=baz
Failed to apply records: Failed to locally apply remote add of
CN=foo,OU=bar,DC=baz: ../lib/ldb/ldb_tdb/ldb_index.c:2012: Failed to
re-index
2018 Mar 15
4
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
On Wed, 2018-03-14 at 16:55 -0400, Justin Foreman wrote:
> Note that I turned up to -d5 but the relevant output didn't seem to change. I just cleaned up my obfuscation for clarity (all referenced DNs were identical):
>
> DRS replication add DN of aca72580-587e-4dab-adee-07a5f8027dfa is CN=foo,OU=bar,DC=baz
> Failed to apply records: Failed to locally apply remote add of
2018 Mar 15
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
No. If I delete that record, the process breaks in the same way on another record in the same OU. I could try deleting all records in that OU to see if it’s something wrong there.
> On Mar 15, 2018, at 2:14 AM, Andrew Bartlett <abartlet at samba.org> wrote:
>
> On Wed, 2018-03-14 at 16:55 -0400, Justin Foreman wrote:
>> Note that I turned up to -d5 but the relevant output
2018 Mar 15
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
After deleting the entire OU the failure happens on a different computer
account in a different OU and so on. I don't think that there's anything
unusual about my computer accounts.
On Thu, Mar 15, 2018 at 2:14 AM, Andrew Bartlett <abartlet at samba.org> wrote:
> On Wed, 2018-03-14 at 16:55 -0400, Justin Foreman wrote:
> > Note that I turned up to -d5 but the relevant
2018 Apr 04
3
Unable to join Windows 2008 R2 server DC to Samba DC
I’m unable to successfully join a Windows 2008 R2 server DC to my Samba4 domain.
I’ve followed the steps on the wiki of joining a Server 2008 R2 DC to a Samba domain. After I reboot the domain controller, I receive a blue screen in regards to a corrupt AD database. I’ve tried Samba v4.6.7 and Samba 4.9.0pre1.
Prior to the reboot, I see the following three events on the Windows DC:
-----
Attempt
2017 Aug 01
0
Fw: Re: Made a join with a netbios name, which already existed, now replication errors
Hello,
now with "ldbsearch --cross-ncs ..." I dont find entries of domain controllers anymore except samba1 and samba2.
sam.ldb seems to be clean now.
But with the DNS-Tool from Windows I can see a lot of entries for samba3, all of them for services like _gc, _kerberos, _ldap, _kpasswd.
Can this be the reason for the error I get when I join samba5 ? Do I have to delete this entries ?
2017 Oct 31
0
Made a join with a netbios name, which already existed, now replication errors
> On 2017.08.02, at 4:22 AM, Rowland Penny via samba <samba at lists.samba.org> wrote:
>
> On Wed, 2 Aug 2017 10:48:50 +0200
> gizmo via samba <samba at lists.samba.org> wrote:
>
>>> No you cannot delete something that is already deleted, but then
>>> deleted objects should be ignored and I think this is fixed in later
>>> versions.
2017 Nov 01
1
Made a join with a netbios name, which already existed, now replication errors
On Tue, 2017-10-31 at 17:37 -0500, Matthew Delfino via samba wrote:
> >
>
> I’m having a similar problem. I just fixed a bad member of my samba
> domain - an samba AD DC that wasn’t working. I demoted it,
> uninstalled Samba and reinstalled, then rejoined the domain.
>
> Everything's replicating nicely. All my users can authenticate. But
> my samba AD DCs are all
2017 Aug 01
2
Fw: Re: Made a join with a netbios name, which already existed, now replication errors
> Get rid of samba3 by demoting it again as you did last time, search
> through sam.ldb for any mention of samba3 and samba4 (you will
> probably have to use '--cross-ncs' with ldbsearch or lbdedit), then
> remove them.
> Now start again with a new DC, but this time, call it anything but
> samba3 or samba4.
Getting worse and worse ....
I demoted samba3 and then also
2018 Mar 15
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
The problem does not happen if I recreate the domain from scratch. I’m able to successfully join 4.8.0 to a 4.6.7 domain built from scratch (just tried it). One thing that I will note is that I also saw SPN creation failures when attempting to join Windows 2008 R2. So it’s not a Samba 4.8.0 problem. It’s a problem with my database (help!).
As for an in-place upgrade, I’m struggling a bit with
2018 Mar 17
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC, unable to upgrade in-place
On Sat, 2018-03-17 at 07:34 +1300, Andrew Bartlett via samba-technical
wrote:
> On Thu, 2018-03-15 at 16:10 -0400, Justin Foreman wrote:
> > Okay. The master build worked on the join. Excellent. So it was 4.8.0 having a problem.
> >
> > I’ve attempted to join 2008 R2 now to 4.8.0 but it still blue screens. Should I start a new thread for clarity’s sake?
>
> So, I
2018 Mar 15
0
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
Okay. The master build worked on the join. Excellent. So it was 4.8.0 having a problem.
I’ve attempted to join 2008 R2 now to 4.8.0 but it still blue screens. Should I start a new thread for clarity’s sake?
Justin
> On Mar 15, 2018, at 3:03 PM, Andrew Bartlett <abartlet at samba.org> wrote:
>
> On Thu, 2018-03-15 at 14:34 -0400, Justin Foreman wrote:
>> The problem does
2019 Nov 03
2
DC with outdated secrets
On Sun, 2019-11-03 at 18:58 +0100, Johannes Engel via samba wrote:
> Hi Andrew,
>
> thanks a lot, however, I am not entirely sure I understand your hint:
> I have 3 DCs in the domain, the third of which is having the issue
> described.
> Now, here is what I did:
> > samba-tool drs replicate DC3 DC2 dc=my,dc=domain --local -k no
>
> Partition[dc=my,dc=domain]
2018 Mar 15
2
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
On Thu, 2018-03-15 at 10:36 -0400, Justin Foreman wrote:
> After deleting the entire OU the failure happens on a different computer account in a different OU and so on. I don't think that there's anything unusual about my computer accounts.
Does it happen when you re-create the domain from scratch with 4.6 or
4.7 and join to 4.8? What about a join of 4.8? What if the source is
2018 Mar 20
1
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC, unable to upgrade in-place
Is there a sensible way for me to manually remove the duplicate SPNs in the mean time?
Justin
> On Mar 17, 2018, at 3:09 PM, Andrew Bartlett <abartlet at samba.org> wrote:
>
> On Sat, 2018-03-17 at 07:34 +1300, Andrew Bartlett via samba-technical
> wrote:
>> On Thu, 2018-03-15 at 16:10 -0400, Justin Foreman wrote:
>>> Okay. The master build worked on the join.
2020 Oct 21
1
Replication fails with (WERR_GEN_FAILURE)
Hello,
I set up a domain with two DCs (dns-backend is BIND9_DLZ) on a Debian 10
system. I used either the Debian-packages or the Packages from Louis
(4.12.8). I created an Ansible-role to setup everything, starting from
installing the packages over doing the provision/join up to change the
settings for bind9. The first DC runs fine. After the reboot services
are all present, allthe SRV Record for
2018 Mar 16
2
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC, unable to upgrade in-place
On Thu, 2018-03-15 at 16:10 -0400, Justin Foreman wrote:
> Okay. The master build worked on the join. Excellent. So it was 4.8.0 having a problem.
>
> I’ve attempted to join 2008 R2 now to 4.8.0 but it still blue screens. Should I start a new thread for clarity’s sake?
So, I think this, the upgrade issues and even the old
servicePrincipalName handling bug is all the same thing.
What
2018 Mar 15
2
Unable to successfully join Samba 4.8.0 or Windows 2008 R2 to a Samba 4.6.7 DC
On Thu, 2018-03-15 at 14:34 -0400, Justin Foreman wrote:
> The problem does not happen if I recreate the domain from scratch. I’m able to successfully join 4.8.0 to a 4.6.7 domain built from scratch (just tried it). One thing that I will note is that I also saw SPN creation failures when attempting to join Windows 2008 R2. So it’s not a Samba 4.8.0 problem. It’s a problem with my database
2018 Apr 25
0
Unable to join Windows 2008 R2 server DC to Samba DC
I have identified and fixed the problem!
The wellKnownObject for the default computer container was missing! I’m wondering if this was a bug from an old version of Samba, as we provisioned the domain with Samba 4.0.3.
I used ldbedit to manually modify the directory and add CN=Computers as the wellKnownObject default computer container. Windows 2008 R2 now joins successfully.
Thanks,
Justin