similar to: Samba] Samba4 problem with Wndows Domain Trust

How would I set the idmap backend to TDB ? Both domain controlers are running Windows 2008 Server. Am 19.12.2016 um 15:44 schrieb Gaiseric Vandal: > Which idmap backend are you using? > > One thing to try is setting the idmap backend for the trusted domains > to TDB (local database file) This is not a great long term solution > since you will not have consistent mappings

Hi Gaiseric, "wbinfo -u" does not show the DOMAIN_B users. "wbinfo -n DOMAIN_B+someuser" works and show the SID of the users, also from Domain_B. "wbinfo -i DOMAIN_B+someuser" does not work. It only works for users of Domain_A. For User of Domain_B, it says: failed to call wbcGetpwnam: WBC_ERR_DOMAIN_NOT_FOUND Could not get info for user Domain_B+someuser

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

Which idmap backend are you using? One thing to try is setting the idmap backend for the trusted domains to TDB (local database file) This is not a great long term solution since you will not have consistent mappings between domains. However it may help determine if the issue is with winbind and idmap in general or with the specific idmap backend (e.g. rid, ad, ldap.) Are the domain

Hi Gaiseric, I have tried that, also in different variations. But the users and groups of DOMAIN_B keep invisible. Below the smb.conf in the meantime state. By the way: kinit works with both, users aof DOM_A and Users of DOM_B. [global] workgroup = DOM_A server string = Samba %v log file = /var/log/samba/log.%m max log size = 50 password server = *

Hi, Here is our smb.conf. Please note that this server uses nss resolution for DOMAIN_B users and idmap_ldap backend to resolve DOMAIN_A users. Trusted relationship between works well for other services between those two domains. Only samba4 fileserver needs to rejoin DOMAIN_A domain (AD 2008 server) every week. #======================= Global Settings

Le 16/08/2017 à 18:18, Rowland Penny via samba a écrit : > Very hard to understand this post, but see inline comments: > > On Wed, 16 Aug 2017 17:47:25 +0200 > Julien TEHERY via samba <samba at lists.samba.org> wrote: > >>> You did say that this machine is joined to the AD domain (DOMAIN >>> A), didn't you ? >> >> Yes >>> If so,

> You did say that this machine is joined to the AD domain (DOMAIN > A), didn't you ? >> Yes > > If so, why, if 'security = ADS' is in smb.conf, are you trying to use > ldap to connect to the AD DC ????? >> Not at all. If it was the case the machine would have never be joined to DOMAIN_A Joining this machine to the 2008 domain (via net ads join..) succeed

On Thu, 2 May 2019 14:05:12 +0800 d tbsky via samba <samba at lists.samba.org> wrote: > > Dear list, > > > > when I connect to a samba AD member server from a windows 10 client > > not joined to the domain, it appears that I always have to connect > > as DOMAIN\USER. Is it possible to configure samba such that it > > always interprets the USER part as

Hi All, Answering to myself, this problem still occurs again and again, every week as I mentioned before. Rejoining the domain each time for samba4 file server is the only workaround. What could be the origin of this kind of problem? Any answer would be helpfull Regards Le 17/07/2017 à 10:12, Julien TEHERY a écrit : > Hello, > > > We recently put in place a trust relationship

Some time back I upgraded a domain controller (Solaris 10) from samba 3.0.x to 3.4.5 In order to support interdomain trusts I am using winbind and idmap allocation with a samba backend. Since the upgrade it appears that samba is no allocating uid and gid's for trusted domain. my smb.conf looks something like:

On Wed, 16 Aug 2017 09:05:32 +0200 Julien TEHERY via samba <samba at lists.samba.org> wrote: > Hi, > > > Here is our smb.conf. > > Please note that this server uses nss resolution for DOMAIN_B users > and idmap_ldap backend to resolve DOMAIN_A users. > > Trusted relationship between works well for other services between > those two domains. Only samba4

Hi Igor, I got stuck now. I did my best. I got stuck at the winbind which I suspected is the reason why the domainA_computer cannot map the domain_B user's home directory. 1. What are the settings of your winbind? 2. Do you use only "winbind" in your libnss_ldap or use "ldap" as well? 3. My winbind works with :- (For both sides) wbinfo -t wbinfo -p wbinfo -u wbinfo

Very hard to understand this post, but see inline comments: On Wed, 16 Aug 2017 17:47:25 +0200 Julien TEHERY via samba <samba at lists.samba.org> wrote: > > You did say that this machine is joined to the AD domain (DOMAIN > > A), didn't you ? > >> Yes > > > > If so, why, if 'security = ADS' is in smb.conf, are you trying to > > use ldap

This is a little of a new experience for me, I am a bit of a novice. I have usually been able to stumble around documentation and other mailing lists to figure out problems, unfortunately I have struck and issue that has me going around in circles ... I have set up a VPN between three locations using openvpn (device = tun ), two satellite locations (referred to as B & C) talking to a

Hi all, we have the following problem: We are running two windows domains, which trust each other. We have several RHEL6-Servers, which act as samba servers with windows domain authentication. Domain A is configured as realm in smb.conf. As long as we run samba3, all users from domain A and domain B are able to be authenticated. "wbinfo -g" lists all windows groups from domain A

Dear list, when I connect to a samba AD member server from a windows 10 client not joined to the domain, it appears that I always have to connect as DOMAIN\USER. Is it possible to configure samba such that it always interprets the USER part as being the account name of the one domain that is configured, and to discard the DOMAIN part supplied by the client? This may be a dumb question, but thanks

Hi Igor, Thanks so much for troubleshooting all this while and we found out none of our configuration is the problem but the source code. Hope that the samba team will modify to a working code so that I can deploy it. Actually my dateline to deploy is coming soon and I do not know what to do now..... when do you think the code will be modified and be released? Thanks so much for your help.

Hi list, I've got Samba 2.0.6 running on Yellow Dog Linux with a 2.2.14 kernel. When I start the PC, it displays the login screen (I have 3 user profiles) and I enter the username and login domain (ie the one operated by Samba). I get an error message stating that the domain login server can't be found. If I then cancel the login, go to the start menu and log off, then login there is

tam taly wrote: > Thanks for Your reply. We are not able understand How to config Source > point If you mean mountpoint, you might not need or want to do anything with it. > and what is the differences between admin and source because here in > this document we are entering separate password for admin and source. If > admin means ICECAST admin then I don't have any user