search for: domain_a

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 ===================================== [global] server string = FILE...

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 fileserver needs to rejoin DOMAIN_A > domain (AD 2008 server) every week. > > #======================= Global Settings > ===================================== >...

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

...------------------------------------------------------------------------------------------------------- winbind enum users = Yes winbind enum groups = Yes winbind use default domain = no winbind trusted domains only = no # The "idmap domains" has been deprecated in 3.4 # idmap domains = DOMAIN_A DOMAIN_B DOMAIN_C # Next two lines restored in 3.4 - but prob don't need idmap uid = 30000-59999 idmap gid = 30000-59999 idmap config DOMAIN_A:backend = ldap idmap config DOMAIN_A:readonly = no idmap config DOMAIN_A:default=no idmap config DOMAIN_A:ldap_base_dn = ou=domain_a,ou=idmap,o=mydo...

...rs once the cache period expired. - it can't talk to domains in "native" mode. However, when I run "wbinfo -u" and "getent passwd" on my 3.0.x machine it will add or update idmap entries in LDAP. 2. Samba 3.4 can read some of the idmap entries from LDAP. Domain_A is Windows 2003 in mixed-mode. Samba 3.0.x is able to populate idmap allocation entries in ldap. Samba 3.4 when running "getent passwd" can see the users from that domain. Domain_B is a Windows 2003 Native domain. Samba 3.4 can not handle those entries. If I manually create the en...

...his 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 whitout any problem. About ldap connector we just thought winbind would use it towards ldap server for DOMAIN_B (Samba 3.5 domain) uid/gid resolution. We actually use nss to resolve those uid/gid > > Can I suggest you rea...

...>>> 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 >> whitout any problem. >> About ldap connector we just thought winbind would use it towards >> ldap server for DOMAIN_B (Samba 3.5 domain) uid/gid resolution. >> We actually use nss to resolve th...

Hi Gaiseric, both packages have been provided as RPM and installed by yum. We didn´t have to compile. "wbinfo -i" shows the correct uidnumber for users of DOMAIN_A, but nothing for users auf the trusted Domain DOMAIN_B. We have another server running Centos 6 and Samba 4.4.4. It shows the same problem: Only users and groups of DOMAIN_A are available. The settings: ldap server require strong auth = no => this makes no change. client ldap sasl wra...

...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 > whitout any problem. > About ldap connector we just thought winbind would use it towards > ldap server for DOMAIN_B (Samba 3.5 domain) uid/gid resolution. > We actually use nss to resolve those uid/gid It doe...

...ry. I am > afraid it will break anytime. > maybe you can give it a try... > > https://bugzilla.samba.org/show_bug.cgi?id=13543 > As Andrew has said, this will not work and why you would want this escapes me ? if it did work, you could end up with a user called 'fred' from DOMAIN_A and a user called 'fred' from DOMAIN_B, so which user would be the one used, the one from DOMAIN_A, or the one from DOMAIN_B, or both ? Rowland

...On 12/19/16 09:16, wp1101412-josef via samba wrote: >> >> Hi Gaiseric, >> >> both packages have been provided as RPM and installed by yum. We >> didn´t have to >> compile. >> >> >> "wbinfo -i" shows the correct uidnumber for users of DOMAIN_A, but >> nothing for >> users auf the trusted Domain DOMAIN_B. >> >> >> We have another server running Centos 6 and Samba 4.4.4. It shows the >> same >> problem: Only users and groups of DOMAIN_A are available. >> >> >> The settings: >...

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

...nning Samba or Windows ? On 12/19/16 09:16, wp1101412-josef via samba wrote: > > > Hi Gaiseric, > > both packages have been provided as RPM and installed by yum. We didn´t have to > compile. > > > > "wbinfo -i" shows the correct uidnumber for users of DOMAIN_A, but nothing for > users auf the trusted Domain DOMAIN_B. > > > > We have another server running Centos 6 and Samba 4.4.4. It shows the same > problem: Only users and groups of DOMAIN_A are available. > > > > The settings: > > ldap server require strong aut...

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 "wbinfo --allocate-uid" doesn´t work. It says: failed to call wbcAllocateUid: WBC_ERR_DOMAIN_NOT_FOUND Could not allocate a uid Yes, I also tried ad backen...

...eed to as A) All machines are running a fairly standard release of Redhat 9.0 and Samba 3.0.20. I am now trying to a domain trust relationship established between each of these sites. When I establish a trust from one of the satellite locations it appears to work ... *net rpc trustdom establish domain_A* Could not connect to server A Trust to domain DOMAIN_A established but from the central location I get the error message *net rpc trustdom establish domain_B* Could not connect to server B [2005/09/14 11:14:21, 0] utils/net_rpc.c:rpc_trustdom_establish(4917) Couldn't verify trusting 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

...itch >> -wbinfo all works. >> -"getent group" and "getent passwd" shows ldap entries of local domain >> and winbind entries of the remote domain. >> -However I still cannot map the home directory of the Domain_B_user >> when I log into Domain_B on Domain_A_XP computer. >> - smbclient //domain_A_PDC/shared -U domain_B/domain_B_user is working. >> >> The command I run on the command prompt (which will work) if I am >> Domain_A_user into Domain_A on Domain_A_XP_computer is "net use x: >> /home". But before I ma...