similar to: Winbind: SID2UID looks in own domain only ?

Hi, I have tested winbind in samba-3.0.25-pre2 and encountered some problems. We have a working config with Linux samba-3.0.23d and W2k3 AD R2 rfc2307bis, but when I switch to 3.0.25 it stopped working. I am not quite familiar with the new configuration directives for idmap, but the old config did not work either with 3.0.25, so I tried to use the new ones. Is there apparent errors in my config

There may be several parts to the problem: 1. Winbind on Samba 3.4.x seems unable to allocate idmap entries (UID/SID or GID/SID) , whether or not the backend is LDAP or TDB. Winbind on Samba 3.0.x is able to create idmap allocation mappings with an LDAP backend. The two problems with Samba 3.0.x are as follows - "getent" would stop showing trusted users once the cache period

IDAMP cache somehow ends up with an unmapped SID2UID entry (i.e value = -1) and the SID2GID entry expires. At this stage winbindd returns unmapped for a SID-to-UNIX-IDs request. This results in smbd giving incorrect group memberships and incorrect resource access, until the SID2UID entry expires. This is surely a bug? Samba version is 3.6.6 as bundled with our current Solaris 10 patch revision

================================================================== "Your brain commands your body to "Run forward! Bend! Scoop up the ball! Peg it to the infield!" Then your body says, "Who, me?" " Joe DiMaggio ================================================================== Release Announcements ===================== This is the latest stable

================================================================== "Your brain commands your body to "Run forward! Bend! Scoop up the ball! Peg it to the infield!" Then your body says, "Who, me?" " Joe DiMaggio ================================================================== Release Announcements ===================== This is the latest stable

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

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

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

Hi, I have two Windows Domains, DOMA and DOMB. A Samba 3.6 Server is a member server in DOMA. DOMA has a (unidirectional) trust relationship to DOMB. Users from DOMB should be able to connect and authenticate at the Samba server. The domain controller of DOMB has the IP 10.35.5.25. During authentication of a DOMB user at a share I get the following log entries: get_dc_list: preferred server

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

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,

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

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

I have 2 domains in my forest. I need to allow users from both DomA (The forest root and the Domain the server is joined to) and DomB to log in. All works fine with DomA, but no one from DomB can log in. wbinfo --domain=DOMB -u returns error looking up domain users. wbinfo -D DOMB returns the following: Name : DOMB Alt_Name : DOMB.local SID :

Hallo. I have problem configuring winbind to authenticate against Active Directory (Windows Server 2003 R2 in native mode). Our net topology seems as follows: - We have PDCs for domain DOMA (i.e.) - there are user accounts for all people on our university. - We have PDC for domain DOMB (DC for our department) that holds computer accounts. - Between DOMA and DOMB is one side trust. So Windows

Hi all, I would like to set CPU Affinity like: vcpu#0 ---> pcpu#0 vcpu#1 ---> pcpu#1 When I start the domain by configuration file defined [vcpus=2] and [cpus="0,1"], the state become as follows. vcpu#0 ---> pcpu#0 or pcpu#1 vcpu#1 ---> pcpu#0 or pcpu#1 So, I have to execute 2 commands to achieve the state. # xm vcpu-pin foo 0 0 and # xm vcpu-pin foo 1 1 # xm

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

Hello I'm experiencing a weird behaviour with idmapping/winbindd. I have two samba controlled domains with one trusting the other and using winbindd to map trusted domain groups and users. This works quite well, but after some time, I can see the unix uid/gid allocated for the trusted domain groups/users being changed, and this keeps on changing approximatively every 2 hours. At