similar to: Issues joining DC

Displaying 20 results from an estimated 6000 matches similar to: "Issues joining DC"

2024 Mar 03
2
Migrate
Dear all. I currently have a Centos7 box running Samba 4.6.5. I would like to increase functional level to latest one. For this reason I created another box (Ubuntu 22.04) with 4.18.9. The plan was to define Ubuntu box as an additional AD server. Once have replica of the AD, move FSMO from Centos to Ubuntu, demote the Centos server and finally increase functional level. On Ubuntu, checked
2024 Jun 14
1
Users appears as SID instead of their own name.
Hello Rowland. You're right. I have to upgrade my current version. But I have tried to do it with same server and with a new one without success. For first trial I tried to compile new version but it doesn't. For the second one I've tried to add a DC to the domain to, after this, move AD primary role to new one, but another time no success. I tried to contact some spanish company
2024 Jun 15
1
Users appears as SID instead of their own name.
Helo Rowland Thanks for your response. I'm using Centos7 as AD server. At this time I'm trying to compile another server with Ubuntu 22.04 and Samba 4.20.1. I'm thinking to merge it as an AD on current domain. If this runs I'll try to move FSMO from old to new. Finally I'll demote old one. Hope this will run and solve the issue. Regarding support, I checked samba.org page
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : Andrew Bartlett [mailto:abartlet at samba.org] > Envoyé : samedi 26 août 2017 12:40 > À : HB; samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote: > > > > > Here is the output of samba-tool dbcheck : > > # samba-tool dbcheck >
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : samedi 26 août 2017 12:00 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > ... > On Sat, 26 Aug 2017 11:28:00 +0400 > > Hi, > > > > I have begun to add a new 4.6.7 DC (following
2024 Jun 15
1
Users appears as SID instead of their own name.
On Fri, 14 Jun 2024 23:25:19 +0200 Josep Maria Gorro via samba <samba at lists.samba.org> wrote: > Hello Rowland. > > You're right. I have to upgrade my current version. But I have tried > to do it with same server and with a new one without success. > For first trial I tried to compile new version but it doesn't. > For the second one I've tried to add a DC to
2024 Jun 14
1
Users appears as SID instead of their own name.
On Fri, 14 Jun 2024 20:07:16 +0200 Josep M Gorro via samba <samba at lists.samba.org> wrote: > Dear group members. > > I have a Samba 4 (4.6.5) running without problems. Er no, you have one really big problem, Samba 4.6.x went EOL (from the Samba point of view) nearly six years ago. > > Now, using a W2022 server enrolled on the AD, when I add someone from > AD to a
2024 Jun 22
2
Failed to fetch machine account password for MYDOMAIN from both secrets.ldb
On Fri, 21 Jun 2024 17:08:39 +0100 Luis Peromarta via samba <samba at lists.samba.org> wrote: > > LP > On Jun 21, 2024 at 12:02 +0100, Rowland Penny via samba > <samba at lists.samba.org>, wrote: > > > > Up until here it was 'DC=mydomain,DC=int', then it becomes something > > different, bad sanitisation ? > > > > Yes :( > >
2024 Jun 15
1
Users appears as SID instead of their own name.
On Sat, 15 Jun 2024 11:11:09 +0200 Josep Maria Gorro via samba <samba at lists.samba.org> wrote: > Helo Rowland > > Thanks for your response. > > I'm using Centos7 as AD server. > At this time I'm trying to compile another server with Ubuntu 22.04 > and Samba 4.20.1. Can I suggest Debian bookworm with Samba from backports instead, this will get you a very
2024 Jun 15
1
Users appears as SID instead of their own name.
On Sat, 15 Jun 2024 12:52:10 +0200 Josep Maria Gorro via samba <samba at lists.samba.org> wrote: > Helo Rowland. > > I think I won't be able to thank you enough for everything you are > doing for me. > > I've tried and seems to run fine. But finally it throws an error and > performs a rollback for all changes on AD. > This is the transcript for the
2018 Mar 12
1
Problem with data base after abnormal shutdown
Hello; last week the power (energy) of the servers fail and it shutdown all. When the power restart in the check I find that the samba4 AD DC have problems. It work, but the users in some of the container or OU dissapear, I mean, when I check with the RSAT the OU in with the user most be, is empty When I try to run # samba-tool dbcheck this is what I have: [root at gtmad ~]# samba-tool
2024 Jun 15
1
Users appears as SID instead of their own name.
Helo Rowland. I think I won't be able to thank you enough for everything you are doing for me. I've tried and seems to run fine. But finally it throws an error and performs a rollback for all changes on AD. This is the transcript for the messages. root at montsec:/usr/local/samba/etc# samba-tool domain join DOMAINNAME DC -U"administrator" INFO 2024-06-15
2020 Oct 14
1
Can I restore a Samba instance from an rsync backup?
Hello, I have Samba 4.3.11 running as an ADDC on Ubuntu 14.04. When I run samba-tool dbcheck, I get the following output: ltdb: tdb(/var/lib/samba/private/sam.ldb.d/DC=CORP,DC=EXAMPLE,DC=CO,DC=NZ.ldb): tdb_rec_read bad magic 0x3f3f3f3f at offset=2993916 ERROR(ldb): uncaught exception - Indexed and full searches both failed! File
2017 Aug 26
0
DC Upgrade from 4.1.7 to 4.6.7
On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote: > > > Here is the output of samba-tool dbcheck : > # samba-tool dbcheck > Checking 1791 objects > ltdb: tdb(/usr/local/samba/private/sam.ldb.d/DC%3DDOMAINDNSZONES,DC%3DCIRAD-REUNION,DC%3DCIRAD,DC%3DFR.ldb): tdb_rec_read bad magic 0xd9fee666 at offset=1115322096 > > ltdb:
2017 Aug 26
0
DC Upgrade from 4.1.7 to 4.6.7
On Sat, 2017-08-26 at 13:46 +0400, HB via samba wrote: > > -----Message d'origine----- > > De : Andrew Bartlett [mailto:abartlet at samba.org] > > Envoyé : samedi 26 août 2017 12:40 > > À : HB; samba at lists.samba.org > > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > > > On Sat, 2017-08-26 at 12:32 +0400, HB via samba wrote: > > >
2017 Aug 26
2
DC Upgrade from 4.1.7 to 4.6.7
> -----Message d'origine----- > De : samba [mailto:samba-bounces at lists.samba.org] De la part de Rowland > Penny via samba > Envoyé : lundi 21 août 2017 16:34 > À : samba at lists.samba.org > Objet : Re: [Samba] DC Upgrade from 4.1.7 to 4.6.7 > > On Mon, 21 Aug 2017 15:52:01 +0400 > HB via samba <samba at lists.samba.org> wrote: > > > Hello all,
2014 Jul 08
2
samba4 replication issues | sam.ldb inconsistency
Hi all, We seem to have some issues with our samba4 ad setup. I posted about this last week already but had received no replies at all so far. :-( What is our situation: two domain controllers (dc1 and dc2), one (separate) fileserver, all running sernet-4.1.7. From the workstations perspective, everything is running as it should, there appear to be no issues. However: something in my
2018 Jul 31
2
Internal DNS migrate to Bind9_DLZ
On Tue, 31 Jul 2018 11:39:56 +0200 Michal <Michal67M at seznam.cz> wrote: > > /etc/named.conf > > # Global Configuration Options > > > > include "/var/lib/samba/bind-dns/named.conf"; > > > > options { > > > > dump-file "/var/named/data/cache_dump.db"; > > statistics-file
2018 Jul 31
2
samba-tool dbcheck "Indexed and full searches both failed"
On Tue, 31 Jul 2018 07:37:38 -0500 Denis Morejon via samba <samba at lists.samba.org> wrote: > Hi: > > I have two samba 4.7.4 DCs. One of them has problems. I can not use > samba-tool on it. Then, when I try to fix It's database It returns: > > ------------------------------------------------------------------------------------------------------------------- >
2023 Mar 03
2
DomainDnsZones bad magic
I've been called back to an old workplace to try to help with some issues that they have and have found that the DomainDnsZones database is not replicating. Everything else in the replication seems to be fine. I ran a samba-tool dbcheck on the affected server and it returns: ltdb: tdb(/var/lib/samba/private/sam.ldb.d/DC=DOMAINDNSZONES,DC=MYDOMAIN,DC=MYCOMPANY.ldb): tdb_rec_read bad magic