search for: bracht

Displaying 10 results from an estimated 10 matches for "bracht".

Did you mean: brachet
2024 May 28
1
Security Implications of "ldap server require strong auth"?
...ing with the correct google search terms :) >> Anyway, this is no longer samba related, so I'll close this thread >> here. And with the hints I got on this list I'll be able to reach my >> goal by myself now :) >> >> Cheers >> Thomas >> -- K?hler + Bracht GmbH & Co. KG Brombeerweg 9 26180 Rastede / Wahnbek Tel: +49 4402-97477-17 Fax: +49 4402-97477-27 E-Mail: Marquardt at koehler-bracht.de <mailto:Marquardt at koehler-bracht.de> www.koehler-bracht.de<http://www.koehler-bracht.de/> ***Facebook*<https://www.facebook.com/people/K%...
2024 May 28
1
Security Implications of "ldap server require strong auth"?
Hello Thomas, we've done the exact same thing: we have a few nextcloud instances bound to Samba (now 4.20, but 4.19 worked too). You HAVE to use "ldaps://<FQDN>" in the "Host" field and "636" in the "Port" field. For the certificates issues: either you create a CA, create the samba certificates and add this CA to the trusted certificate
2023 Jan 17
1
Missing security descriptor reference domain
Hi, to check my domain I ran dcdiag /s:srv-kb-dc1 Windows PC an get some errors/warnings: The following text is google translated of the german report. I don't know how close this translation is to the english orginal: Starting test: CheckSDRefDom A security descriptor reference domain is missing from the application directory partition DC=ForestDnsZones,DC=local,DC=dom. The msDS-SD
2023 Jan 17
1
Default route mandatory on a Samba member server?
Am 17.01.23 um 14:54 schrieb Kees van Vloten via samba: > Op 17-01-2023 om 13:49 schreef Peter Milesson via samba: >> Hi folks, >> >> Is a default route and gateway mandatory on a Samba member server? >> >> The AD DCs, the workstations and the Samba member server are on the >> same network segment. As the member server only serves files to the >> local
2024 Jan 05
1
Cleanup after demoting an offline DC
Hi, I demoted an outdated and offline DC following to: https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC Everthing appears to work well but there is still one, perhaps minor, question regarding to the dns SOA-record: The zone _msdcs.samdom.example.com still lists the demoted server in the SOA record. Is it ok to manually change it to fsmo holder dc or an other dc? Thanks in advance
2023 Jan 11
1
problems with sysvol aft
Hi, I plan to upgrade/replace my somewhat crippled and outdated samba 4.7.4 domain controller. The OS is an openSUSE-Leap-42.3 which had no packages for a samba-ad-dc. These packages have been introduced in successor openSUSE releases starting with Leap-15.0. Leap-15.0 comes with samba 4.7.11. So I set up a new Leap-15.0 host and joint it as a dc controller. I set up the sysvol replication
2023 Jan 13
2
problems with sysvol after fsmo transfer
Am 13.01.23 um 11:31 schrieb Rowland Penny via samba: > > On 13/01/2023 09:53, Markus Dellermann via samba wrote: >> Hi Thorsten, hi Rowland, >> Just one hint from me: >> openSUSE-samba-Packages are normally mit-kerberos based. >> For DCs it could be better to use the heimdal-based >> >> There are some convenient repos on openSUSE-Build-Server.. >>
2023 Jan 12
1
problems with sysvol after fsmo transfer
Am 12.01.23 um 14:03 schrieb Rowland Penny via samba: > On 12/01/2023 12:51, Rowland Penny via samba wrote: >> On 12/01/2023 12:28, Thorsten Marquardt via samba wrote: >>> srv-kb-dc1:~ # klist >>> Ticket cache: DIR::/run/user/0/krb5cc/tkt >> What OS is this ? the old host: srv-kb-primdc:~ # cat /etc/os-release NAME="openSUSE Leap"
2023 Jan 12
1
problems with sysvol after fsmo transfer
Am 12.01.23 um 12:25 schrieb Rowland Penny via samba: > > On 12/01/2023 10:53, Thorsten Marquardt via samba wrote: >> Thank you so far. But unfortunately I could not fix the problems. So I >> decided to start over again at a situation where all the fsmo roles >> resides on the old controller. >> >> Here is a transcript of what I did and the errors reported:
2023 Jan 12
1
problems with sysvol after fsmo transfer
Thank you so far. But unfortunately I could not fix the problems. So I decided to start over again at a situation where all the fsmo roles resides on the old controller. Here is a transcript of what I did and the errors reported: The inititial position srv-kb-dc1:~ # samba-tool fsmo show SchemaMasterRole owner: CN=NTDS Settings,CN=SRV-KB-PRIMDC,CN=Servers,CN=Default-Fi...