similar to: Problem create trust between Samba AD and MS Windows AD.

Hello. I faced the problem of building trust between Samba AD and MS Windows AD. In Ubuntu 23.10 (IP-address 10.10.28.223/24) and installed Samba 4.18.6 from base repository was deployed the domain smbub.test. The commad to deployed: samba-tool domain provision --use-rfc2307 --realm=smbub.test -- domain=SMBUB --server-role=dc --dns-backend=BIND9_DLZ --backend- store=mdb --backend-store-size

Hi, No replies unfortunately. Unsure why. We searched the list, and we found little discussion on the subject of trusts. We see occasional questions, but they are often left unanswered, like this one. If someone could point us to some good up-to-date docs on trusts with samba then we would really appreciate it. We setup a test environment (one samba 4.9.4 testad2 AD, one native windows

Hi Stefan, Thanks for your input. I'll check the dns stuff. I put resolvers for both domains as primary and secondary on both machines, but I guess that's not good enough. I'll look into setting up a (query logging) dns proxy, that should tell us at least who is asking what. Any chance to share that (german) article you wrote? My german is not perfect, but good enough to

Hai Maurik-Jan, Stefan's work can be found here, i'm reading it myself and its really good.

Hi MJ, Am 28.02.2019 15:31, schrieb mj via samba: > Hi Stefan, > > Thanks for your input. I'll check the dns stuff. I put resolvers for > both domains as primary and secondary on both machines, but I guess > that's not good enough. > NO, it's not good enough ;-) Setting up a DNS-Proxy is real easy. Just a few lines :-). > I'll look into setting up a (query

Hi Stefan, others, Just to report back that things work very nicely now that DNS is using one dns proxy that resolves both AD domains. I am testing now with a 'full' two-way trust, and everyhing seemed to work, including the tests from samba-tool and from windows "domains and trusts" perspective. From an administrative point of view, the fact that your have to add

Now I have a some time to answer, maybe a few of your questions. Am 26.02.19 um 20:59 schrieb lists via samba: > Hi, > > No replies unfortunately. Unsure why. There are still a lot of questions open and I think a lot of things have to be done. > > We searched the list, and we found little discussion on the subject of > trusts. We see occasional questions, but they are often

Thanks everybody! The sudden burst of help (both on- and offlist) is much appreciated. :-) I'll get back to my test setup next week, and try again with these new insights. MJ On 2/28/19 3:46 PM, L.P.H. van Belle via samba wrote: > Hai Maurik-Jan, > > Stefan's work can be found here, i'm reading it myself and its really good. > >

Hi, Having read the release notes on the status of trusts within samba, we see for 4.9 > "improved support for trusted domains" but we also always see these messages: > "Both sides of the trust need to fully trust each other!" and > "DCs of domain A can grant domain admin rights in domain B" What we would like to achieve is a one-way incoming trust

Hello, I have been using flags in public folders for quite a while with no problems. Once the flags were added to all clients (Thunderbird), they were visible and synchronized properly. Now I have added some new flags, and in the dovecot-keywords files I see that I am now using more than 25 flags (in which case they are not stored using an additional letter in the filename). Now I see that

On 15/10/2019 13:56, ASW Global via samba wrote: > I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10

While debugging a different problem, I used "doveadm dump" to show information about a maildir folder; it happily reported values from dovecot.index and dovecot.index.log (confirmed by strace): [...] messages count ........... = 978 seen messages count ...... = 967 [...] However, mail clients reported different values, I guess because the Seen flags were actually stored in the

Hi all, I was testing the 4.3.0 version to see what is available with trust relationship but except having my DCs telling me there are trust relationship and using the global catalog to perform search (but with only search for object in a.domain.tld when search is performed against dc.a.domain.tld) I can do nothing else. My own knowledge on that subject is quiet null so I come to you asking some

I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10 client to the Samba domain without any issues. The

Until yesterday replication between my two DCs (boa and cobra) was running fine. Now I am observing one direction boa->cobra being stuck. I noticed this with a missing update of a DNS entry, but samba-tool drs showrepl confirms? Output of cobra shows plenty entries like the following (including just he first of each type): ==== INBOUND NEIGHBORS ====

I figured it out myself. The kerberos configuration on the old dc cobra was bad ? no clue why it worked at all until yesterday. After fixing it, testing with kinit, and restarting the dc processes it resumed replication. Joachim Von: Joachim Lindenberg <samba at lindenberg.one> Gesendet: Friday, 19 July 2019 16:54 An: samba at lists.samba.org Betreff: replication stuck? Until

On 2018-09-12 09:44 AM, Jeremy Allison via samba wrote: > On Wed, Sep 12, 2018 at 09:30:19AM -0700, Ray Klassen via samba wrote: >> >> and from the what the hell department. I did it. Comparing >> >> https://docs.microsoft.com/en-us/windows/desktop/api/lmshare/ns-lmshare-_session_info_1 >> >> >> and >> >>

Can Somebody have a look !? Or an Idea. How bind can resolve the second cname ._mscds. I can take every other cname for my second samba4 but the: a441f8f9-629d-43c4-bce6-a5dfba1e4ad9._msdcs NODE1 is: 02284f45-de16-4125-a795-3b614f540ef7 NODE2 is: a441f8f9-629d-43c4-bce6-a5dfba1e4ad9 So Replication from NODE2 to NODE1 works fine: UpdateRefs OK for

HI, I have a Windows 2003 as AD PDC. My intention is disable this Windows and use Samba4 instead. I have compiled Samba 4.1.12 on Debian 7 without problems. I followed Samba Wiki to Join this machine to Win domain, without to do the Samba4 provision steps, as mentioned. The join process occurs without errors and all strutcture of Wind2003 was replicated to Samba4. All modifications done on

Hello list, I am testing Samba 4.8.0rc3 and see following output every drepl-Service run: DRS replication add DN of ad1894a9-07f8-4ae2-8e5c-2a15ed9ed8b3 is CN=BUILDHOST,OU=Domain Controllers,DC=samdom,DC=local ldb: ../lib/ldb/ldb_tdb/ldb_index.c:1837: unique index violation on @IDXDN in CN=BUILDHOST,OU=Domain Controllers,DC=samdom,DC=local, conficts with 蔁墁o癣No甬瓧k in