similar to: Authentication against AD

Hi everyone, I have two domains with a two way trust (DomA and DomB). When users from DomA (on a DomB Linux PC) access sysvol on DomB's DC using smbclient everything works: # smbclient //DomB /sysvol -Udoma\\user -c 'ls' -k . D 0 Thu Jan 9 13:53:03 2020 .. D 0 Thu Jan 9 14:28:29 2020 domb

Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've got Samba set up with an LDAP backend, I've extended my NDS schema, and I've got users in this new domain set up successfully and authenticating. I've decided that the best, most seamless way to migrate my domain is to create a new domain which will run alongside the old domain. A two-way trust

hi, it?s me again :( i?m still not able to use idmap_rid in a trusted domain environment (samba v3.0.20b Sernet). well, to be clear: NSS is not working (id, getent passwd <user>, ...) so samba does not find the posix information for any user from a foreign domain it?s working in a single domain with ##################################### # WINBIND - Settings idmap backend =

Hello, I did join 2 sites using an IPSEC tunnel, and made one domain trust the other (2 small Samba DC based domains with about 10 users in each) I first had resolving issues until I decided to keep only one WINS server for both networks (though this is still an issue to me because if for any reason the tunnel is broken, I have no longer WINS on one side). Finally here is my setup : Network A

Hello all. I've set up a testing environment with two Windows DCs. The first, called DCA, is serving the domain DOMA and is running Windows 2003. The second is called DCB and serves DOMB on Windows 2008. The Samba machine I'm setting up (named ULYSSES) should be able to authenticate users from both domains for shell login. I've installed Samba 3.2.3 as a Debian package and closely

hi list, just for my knowledge -> we have a working PDC / BDC infrastructure for our domain DOMA, where PDC trusts another PDC from DOMB (all samba v3). when PDC from DOMA goes down, is the trust still valid or do we have to setup the trust on *both* DCs from DOMA (net rpc trustdom establish DOMB ... )? is that possible at all? thx&greez -- Michael Gasch Max Planck Institute for

Hi Guys, I would like to implement File Sharing in a WAN environment, however there are some issues which I can't figure out. 1. Users are distributed across 3 countries. (Server is physically located in CountryA) 2. Logins are different across all 3 countries. a) They are logging into different domains. eg: DomA; DomB; DomC etc 3. My File Share is running Samba 2.2.7 4. Local

Hello Community, I am facing the following question: how is it possible to share malboxes between domains? Example: - 2 domains present on the same dovecot: domA and domB - userA at domA - userB at domB userA at domA wants to share his mailbox to userB at domB (again same server)? Thank you for your help. Greetz

This one doesn't make any sense to me. What's worse, it seems to occasionally work and sometimes not. I am attempting to log into a domain (DOMA let's say) and I only have an account on DOMB. When DOMA's Samba PDC attempts to create a UNIX account for me, this is what happens: [2005/01/04 15:47:15, 3] auth/auth_util.c:smb_create_user(53) smb_create_user: Running the command

I'm currently building a Samba3-based domain (DomA) that has a trust relationship with an existing production NT4 domain (DomB). DomA uses an LDAP backend. The LDAP server is local on the PDC and is dedicated to such use. DomA runs Samba 3.5.6 on Debian 6.0. DomB is an old-timer: NT4 domain that's running for ages. The trust relationship has been established: DomA trusts DomB. Clients

Hi everybody. When using the command: # net rpc trustdom list what is the difference in output between: The "trusted" domains list and "trusting" domains list? Which operations are performed in both actions? My example: net rpc trustdom list Trusted domains list: DOMA S-1-5-21-790525478-1844823847-725345543 DOMB

On Fri, 01 Dec 2017 03:47:26 -0500 Mark Foley via samba <samba at lists.samba.org> wrote: > > Yeah, I saw that, and I read the developer's comment. Frankly, I > don't get it. Seems to me winbind behaviour should be the same, AD/DC > or domain member. And it should deliver to programs the id they > expect (w/o domain name), regardless of the use being made. I don't

I've a problem with trusting domain authentication , I've searched the newsgroup but found no answer . The configuration is very simple . A windows 2000 domain (DOMA) , which contains the samba server , and a Windows 2003 domain (DOMB). The two are trusted by a bidirectional trust . The problem is that users from the 2003 domain can't get authenticated by the samba server and are

I am trying to get two Samba PDC/Domains setup with a trust between them. They are separate domains because they are separate companies (one is a subsidiary of the other) located in different cites. I am using Centos 5.1 x86_64 and Samba 3.0.28a packages built by me from Fedora 8 source RPMs. Based on what I have read, in order to do the trust thing I need to use Winbind/idmap to handle the non

Hi, Between Samba 3.4.15 and 3.5.11 there was a change in how 'wbinfo -r' gathers the groups of which a given user is member of. Assume there is a Windows 2003 domain called DOMA. This domain has a child domain DOMB. On DOMA there is a security group G-DL-DOMA which has domain local scope. On DOMB there is a security group G-U-DOMB which has universal scope. Group G-U-DOMB is member

Hello. I've got a samba4 domain member server. It works fine for the joined domain, but I'm not able to let user from a different domain get access. This worked fine on my samba3 member server, but I don't remember if I did anything special. I do have authentication set on the AD object for the users in question and we have a one-way trust with the other domain. All DCs are Windows

Hi All, Wonder is someone can help? We have mixed windows & Linux boxes in DomA network. Afaik all DomA clients are blocked and direct connection to DomB are not possible by design & for security. DomA DC(Windows) -- trust --> DomB DC(Windows) ^ | DomA Linux Client(DALC) winbind Samba 3.0.33 For some reason DomA Linux Client attempts ldap connection to all DomB DC once in 5 to 10

Hi, I am having difficuly deleting and renaming files with users from a foreign domain using acls. My setup is as follows : I have two Samba (3.0.14a)/LDAP domains connected via a VPN (OpenVPN) with a bi-directional trust relationship established. The trust relationship appears to be working correctly. I can log on onto PC's at either end on either Domain :) and the browse lists of both

If I create directory on the DomB DC named /test and create the following share: [test] path = /test read only = No acl_xattr:ignore system acls = yes DomA users can access that through Windows on DomB without issue, but if I set [sysvol] to "path - /test they cannot". There appears to be some special magic with [sysvol] I am unaware of. I'm not seeing any

The company I work for is split across two sites, each site has its own domain. The local end is a Samba server (DomA) with about 50 users, the remote end is NT4(DomB) with about 150 active users (400+ usernames in userlist). The two sites are connected over a VPN (Internally DomA=172.16.1.0/24, DomB=10.1.0.0/16) and the two domains trust each other. Users from either site regularly visit,