similar to: [Samba4] 4.3.0 trust relationship

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

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, 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

My bad. Trust relationship is created and can be check using winbind: wbinfo -u -> get local users list wbinfo -u --domain=trusted.domain.tld -> get trusted domain users list (short domain can be used too) It can also be validated using --local-dc-username and --local-dc-password switches: samba-tool domain trust validate trusted.domain.tld \ --local-dc-password=trustedAdminPass \

Good afternoon. We ran some more tests. Trust is built between domains on Samba AD and MS Windows Server 2012R2 and MS Windows Server 2019 with any updates and any versions of the schema. Remote validation proceeds normally when building trust on the part of Samba AD: the remote server is detected. We also carried out the following test - A domain controller based on Windows Server 2019 was

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

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

Hello Samba List, I have a desktop with a clean full install of Windows 10 Pro 1709. I have an entry in the Samba 4.7 AD for the machine account (from when it was Windows 7 Pro). Windows 10 appears to join the Domain successfully. When I try to log in with the DOMAIN\Administrator account I get the Windows error:- "The security database on the server does not have a computer account for

One my 4.8 box I recently made a silly mistake sending a mail from the command line, along the lines of: mkn@shrewd$ mail test@knigma.org -c test@knigma.org Subject: test test EOT mkn@shrewd$ WARNING: RunAsGid for MSP ignored, check group ids (egid=1001, want=25) can not chdir(/var/spool/clientmqueue/): Permission denied Program mode requires special privileges, e.g., root

Since upgrading our DCs to Sernet Samba v4.5.1 we are experiencing problems using Remote Desktop from Windows boxes. The rather useless and completely misleading error message states: "The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the

Running a mix of samba versions (3.6.25 and 4.5.1) in two domains- one "classic" (with samba domain controllers) and one AD (with windows domain controllers.) The eventual goal is to drop the classic domain in favor of the AD domain. Also trying to move from samba 3.x to 4.x since Samba 3 is EOL'd. the "wbinfo -u" command will list users in the servers domain

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

can you try : smbclient //SERVER.DOMAIN.TLD/netlogon -k bet that works.. Louis >-----Oorspronkelijk bericht----- >Van: heinz.hoelzl at gvcc.net >[mailto:samba-bounces at lists.samba.org] Namens Heinz H?lzl >Verzonden: dinsdag 14 april 2015 10:55 >Aan: samba at lists.samba.org >CC: pug at felsing.net; schnaggy at schnaggy.de >Onderwerp: Re: [Samba] samba 4.2 RDP

Just a though as I was passing in the neighbourhood: does your Terminal Server have related SPN (ServicePrincipalName) created on computer objects? servicePrincipalName: HOST/W7AD-02 servicePrincipalName: HOST/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02.ad.domain.tld servicePrincipalName: TERMSRV/W7AD-02 HOST/<hostname> should exist on all computers, that's just to be

Hi I have setup a Samba AD and connected a Windows 7 machine to the AD... I'm having problems getting the Remote Desktop Users group to work... [root at bart private]# samba-tool group addmembers "Remote Desktop Users" mj ldb_wrap open of secrets.ldb Added members to group Remote Desktop Users [root at bart private]# samba-tool group listmembers "Remote Desktop

@Andrew: I expect these lines came from RDP issue workaround which should be happening with previous Samba version. I removed all these lines as now, with 4.2.2 Samba version RDP and RSAT are working well without them. I removed also each and every idmap lines, commented most of winbind lines too and now my smb.conf is: ------------------------------------------------------------ [global]