similar to: Using two SIP-Domains with asterisk

Hi there, This is most likely something very basic which I'm not seeing right now. I have a Samba-server, which is running in security = domain, and it's a member of that domain (DOMAINA). The domain is a Win2003 domain. That domain has established a trust with another domain (DOMAINB). There's a Windows terminal server TERMSRV which is a member of DOMAINA, but a user from DOMAINB

I have been trying off and on for some time now to get an interdomain trust relationship going between two samba pdc machines (DomainA=trusted & DomainB=trusting). Both pdc's are running on Solaris boxes and NIS is involved (I doubt there is a NIS complication just because I can use accounts on DomainA on DomainB's samba, as long as I add them using smbpasswd manually). The situation

config smb.conf [global] realm = DOMAINB workgroup = DOMAINB security = ADS template homedir = /home/%U template shell = /bin/bash winbind expand groups = 1 winbind separator = + winbind use default domain = Yes idmap config domainb : range = 3000001 - 4000000 idmap config domainb : backend = rid idmap config domainc : range = 2000001 - 3000000 idmap config domainc : backend = rid

I've pored through the documentation, wiki, lists, etc, and I can't seem to come to a concise conclusion on how to accomplish this. My specific scenario is the following. I have a samba PDC domain called domainA, and an AD domain called domainB. domainA and domainB are different named domains, and they each authenticate logins and credentials on their own turf. The users on domainA

I am not sure if this is relevant root at sambaPDC:~# /usr/local/samba/bin/net rpc trustdom establish DomainB Enter DOMAINA$'s password: Could not connect to server DomainB_DC Trust to domain DomainB established root at sambaPDC:~# root at sambaPDC:~# /usr/local/samba/bin/net rpc trustdom establish DomainC Enter DOMAINA$'s password: Could not connect to

Hello, I have a client that wants to have a dedicated smtp sending host. But they have 2 separate domains then that don't want to have share IP address. The reasons from this is long and drawn out. Is it possible to setup postfix in a virtual host config, like apache for example, such that, domainA.com listens and sends on one IP address and domainB.com listens and sends on another address.

The trusts aren't really working with Windows 2008 either (where DOMAINC is the Windows 2008 domain.) # /usr/local/samba/bin/net rpc trustdom establish DOMAINC Enter DOMAINA$'s password: Could not connect to server DOMAINC_DC Trust to domain DOMAINC established # Active Directory Domains and Trusts MMC on the Windows 2008 AD DC (DOMAINC_DC) seems to think the

I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try

I have a samba classic domain, called it "DomainA." All domain controllers and servers are running 3.6.25 on Solaris 11. The PDC and BDC use an LDAP backend for unix, samba and idmap data. Member servers use LDAP backend for unix accounts, so the underlying unix and group accounts are consistent. There is a trust relationship with Windows 2008 AD domain

Just when I thought I had idmap changes correct for 3.6, I realize I have a setup that's not quite right: getent passwd ->No AD users getent passwd DOMAINA\\aduser aduser:*:1001601:1000513::/home/aduser:/bin/bash Shouldn't "getent passwd" show both local and AD users? Samba has had such an identity crisis over the years with idmap documentation. Depending, on where you

I tried recreating the trusts. I start by setting up trusts on Windows side, using Active Directory Domains and Trusts on the DomainB AD server. . I specify the the samba domain (DOMAINB) but before I can even specify trust type or direction I get the following: Cannot continue Trust relationship can not be created… The local security authority is unable to obtain an RPC

Greetings, We are currently experiencing logon problems with a trusted domain user(s). Example: We have DomainA and DomainB DomainA and DomainB both have workstations joined on their respective domain. DomainA and DomainB both have trust relationships. DomainA trusts DomainB and vise versa. DomainA is where being served by a Samba PDC, while DomainB has a PDC using Windows NT 4.0 Server When

Hi, I'm using ntlm_auth to authenticate users in freeradius. My samba server is joined to DOMAINA. When I run ntlm_auth --username=domainauser everything works great. When I run ntlm_auth --username=domainbuser it fails because the user does not exist in domaina which the server is joined to. If I run ntlm_auth --username=domainbuser --domain=domainb it works great. I was wanting to do

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Another wrinkle with vacation replies. I have user forwarding their mail from one domain to our mail server with the vacation reply set. Here is the dovecot script file: require ["fileinto", "vacation"]; # BEGIN VACATION vacation :days 30 :from "joe at domainB.edu" :addresses ["joe at

Hello, I've two domains : * DomainA with a Windows 2016 AD * DomainB with a Samba 4.8.4 AD (with DNS internal Backend and with a second samba AD in 4.6.7) With DNS tools, in the Windows 2016 AD i can set "Conditional forwarders"  to DomainB with the IP of the Samba 4.8.4 (checked green) But with the tools in DomainB, I can't set a "Conditional forwarders" to

I have a problem with Samba: I want to make trust between two Samba domains. I have setup the trust on the DOMAINB server then on the Samba DOMAINA server "net rpc trustdom establish DOMAINB" I then get the following: Password: [entered password] Could not connect to server SERVERB [this is the PDC for the DOMAINB domain] Trust to domain DOMAINB established When I then try

2017-08-31 16:29 GMT+02:00 Rowland Penny via samba <samba at lists.samba.org>: > On Thu, 31 Aug 2017 16:08:00 +0200 > mathias dufresne <infractory at gmail.com> wrote: > > > 2017-08-31 15:54 GMT+02:00 Rowland Penny via samba > > <samba at lists.samba.org>: > > > > > On Thu, 31 Aug 2017 15:28:57 +0200 > > > mathias dufresne via samba

On Thu, 31 Aug 2017 16:27:12 +0200 mathias dufresne <infractory at gmail.com> wrote: > PS: the short way to explain %u is adding domain/workgroup to > username is the fact we are using trust relationship? > Probably, what you have to get your head around is this: The users 'fred', 'DOMAINA\fred' and 'DOMAINB\fred' are all different users. Winbind will

Hi, I have a two way trust setup with Samba 3.0.25b (DomainA) and Windows 2003 (DomainB). ./net rpc trustdom list Password: Trusted domains list: DomainB S-1-5-21-xxxx096750-1475201110-303849303 none Trusting domains list: DomainB S-1-5-21-xxxx096750-1475201110-303849303 My Windows XP machine is in the Windows 2003 DomainB, and the users home areas are in

I 've spent the last week troubleshooting a configuration issue regarding samba not being able to connect to other domains beside the domain of which it 's a member server (samba 3.0.14a, krb 1.3.6, w2k). I have some doubts perhaps someone can answer... Suppose this scenario: Samba name : SAMBA Main domain: DOMAINA (domain controller = DCA) Others domains : DOMAINB, DOMAINC (domain