similar to: interpret non-domain users as domain users?

Displaying 20 results from an estimated 20000 matches similar to: "interpret non-domain users as domain users?"

2019 May 02
1
interpret non-domain users as domain users?
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
2017 Aug 16
2
SAMBA4 - Trusted relationship lost every Weeks
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
2010 May 05
2
samba 3.4.5 idmap alloc broken - more details
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
2017 Aug 13
2
SAMBA4 - Trusted relationship lost every Weeks
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
2017 Aug 16
2
SAMBA4 - Trusted relationship lost every Weeks
> 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
2017 Aug 17
1
SAMBA4 - Trusted relationship lost every Weeks
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,
2016 Dec 19
2
Samba] Samba4 problem with Wndows Domain Trust
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
2016 Dec 22
1
Samba4 problem with Wndows Domain Trust
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
2004 Oct 31
2
Re: Trusting and trusted domain (home mapping) problem
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
2016 Dec 19
1
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
2019 May 02
0
interpret non-domain users as domain users?
> 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?
2010 May 04
0
samba 3.4.5 idmap alloc broken
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:
2017 Aug 16
0
SAMBA4 - Trusted relationship lost every Weeks
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
2016 Dec 20
1
Samba4 problem with Wndows Domain Trust
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 = *
2017 Aug 16
0
SAMBA4 - Trusted relationship lost every Weeks
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
2005 Sep 14
0
Message "Couldn't verify trusting domain account. Error was NT_STATUS_LOGON_FAILURE" while attempting "net rpc trustdom establish domain_B"
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
2000 Jan 10
6
cups, samba and print queue....
Hello! we are using cups 1.0.4 and samba 2.0.6 here. windows client can print correctly, but they can not see queue status. the print manager of windows allways shows blank. how to solve this problem? Any body got success to let windows client see the queue of the server ?? thanks for help .... Best Regards, Tbsky
2018 Jul 22
2
winbind behavior question
2018-07-19 23:59 GMT+08:00 Rowland Penny via samba <samba at lists.samba.org>: > > Please see inline comments. > > On Thu, 19 Jul 2018 23:44:48 +0800 > d tbsky <tbskyd at gmail.com> wrote: > >> thanks a lot for the quick help. I remember in old days it happened >> sometimes. but after upgrade rhel 7.5 (from samba 4.6.x to 4.7.1) and >> samba DC
2018 Jul 23
2
winbind behavior question
On Mon, 23 Jul 2018 14:48:00 +0800 d tbsky <tbskyd at gmail.com> wrote: > 2018-07-22 17:44 GMT+08:00 d tbsky <tbskyd at gmail.com>: > > 2018-07-19 23:59 GMT+08:00 Rowland Penny via samba > > <samba at lists.samba.org>: > >> > >> Please see inline comments. > >> > >> On Thu, 19 Jul 2018 23:44:48 +0800 > >> d tbsky
2007 Jan 29
5
memdisk 3.35 + ghost problem
HI: i just trying memdisk that comes with syslinux 3.35. i try to load a dos image, which contains ghost verison 8.3 and ghost version 11. both version of ghost hangs when start-up. memdisk that comes with 3.40 pre is ok. and many earlier versions is ok too. i try some parameter like "safeint","raw". but none work. i use memdisk with pxelinux, below is part of my