Displaying 20 results from an estimated 10000 matches similar to: "idmap config range problem"
2016 Dec 14
0
wbinfo -u does not listed trusted users, wbinfo -n works, idmap not working
On a samba 4.5.1 domain controllers (PDC and BDC), classic domain ,
LDAP is used as the backend for both user accounts AND for the idmapping
of trusted domains . Partial smb.conf below
workgroup = THISDOMAIN
security = user
passdb backend = ldapsam:ldap://xxxxxxxxxxxxxxxxx
idmap config * : backend = tdb
idmap config * : range = 5000-6000
idmap config THISDOMAIN :
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
2016 Dec 19
1
wbinfo -u does not listed trusted users, wbinfo -n works, idmap not working
On both Samba 4.5.1 member server and Samba 3.6.25 member server I tried
the following command
wbinfo –set-uid-mapping=35049,S-1-5-21-xx-xx-xxx-xxx
this should have created a mapping entry consistent with the one on the
domain controller for a trusted user
But I got the following error
failed to call wbcSetUidMapping: WBC_ERR_NOT_IMPLEMENTED
As far as I can tell from network
2020 Feb 29
0
idmap range and xidNumber
On 29/02/2020 16:30, Alexander Kushnirenko wrote:
>
> You are right, this is used on Unix domain member
I know I am right, I put that in the wiki ;-)
>
> Well on DC I see files owned by unix user with UID=3000000 in
> /var/lib/samba/sysvol/, and when I look on the same SYSVOL share from
> windows world I see that the file is owned by BUILTIN\Administrator
> user
2017 Jul 10
0
domain member idmap wbinfo WBC_ERR_DOMAIN_NOT_FOUND
On Mon, 10 Jul 2017 14:17:42 +1000
Tom Robinson via samba <samba at lists.samba.org> wrote:
> Hi,
>
> I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5
> bringing across all the user accounts. The samba 3.6.23 we set up
> with smbldap as an NT Domain with OpenLDAP. After a lot of effort the
> classic upgrade worked well but now I'm a bit stuck with
2017 Jul 10
1
domain member idmap wbinfo WBC_ERR_DOMAIN_NOT_FOUND
On 10/07/17 17:05, Rowland Penny via samba wrote:
> On Mon, 10 Jul 2017 14:17:42 +1000
> Tom Robinson via samba <samba at lists.samba.org> wrote:
>
>> Hi,
>>
>> I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5
>> bringing across all the user accounts. The samba 3.6.23 we set up
>> with smbldap as an NT Domain with OpenLDAP. After a
2009 Oct 08
0
samba PDC + BDCs + LDAP
Hi,
I'm not a seasoned samba user but I do have a little experience with it
(mostly small setups with plain smbpasswd file and a few workstations).
I also have some experience with OpenLDAP and I've even written some
objectclasses and attributes when the standard ones weren't enough
However, I'm trying to set up a midsized network using LDAP for SSO and
I can't make samba
2018 Jan 16
2
idmap limit?
Ok, you are completely right. Here are the real numbers with changed
user names:
drwx------ 43 DOM\user1 DOM\domain-user 4096 Jan 10 08:00 user1
drwx------ 5 DOM\user2 DOM\domain-user 4096 Jan 11 08:13 user2
drwx------ 92 DOM\user3 DOM\domain-user 4096 Jan 16 08:39 user3
drwx------ 3 133265 DOM\domain-user 4096 Sep 7 2015 user4
drwx------ 7
2018 Jan 16
2
idmap limit?
Hi,
no, that's my fault. I changed the UIDs and user names in my "ls -l" to
unpersonalized/example data for my mail and didn't think about putting
these values into the range. A better unpersonalized data example would
look like:
----------
drwx------ 43 DOM\user1 DOM\group 4096 Jan 10 08:00 user1
drwx------ 5 DOM\user2 DOM\group 4096 Jan 11 08:13 user2
2017 Jul 10
2
domain member idmap wbinfo WBC_ERR_DOMAIN_NOT_FOUND
Hi,
I've done a classic upgrade to from samba 3.6.23 to samba 4.6.5 bringing across all the user
accounts. The samba 3.6.23 we set up with smbldap as an NT Domain with OpenLDAP. After a lot of
effort the classic upgrade worked well but now I'm a bit stuck with idmapping.
The new AD DC is running 4.6.5 on CentOS7 and I can connect using ADUC. I set up a separate AD DM on
a another CentOS7
2018 Jan 16
0
idmap limit?
On Tue, 16 Jan 2018 16:54:17 +0100
Andreas Hauffe via samba <samba at lists.samba.org> wrote:
> Ok, you are completely right. Here are the real numbers with changed
> user names:
>
> drwx------ 43 DOM\user1 DOM\domain-user 4096 Jan 10 08:00
> user1 drwx------ 5 DOM\user2 DOM\domain-user 4096 Jan 11
> 08:13 user2 drwx------ 92 DOM\user3
2003 Aug 27
1
Again: restriction on workgroup name length ?
Hi,
I have checked out the cvs tree on Monday, Aug 25 which includes
your patch, built and installed it but without success:
log.nmbd:
[2003/08/27 16:34:00, 0] nmbd/nmbd_nameregister.c:(73)
register_name_response: Answer name EMEA.CORPDIR.NE<00> differs from question name EMEA.CORPDIR.NET<00>.
[2003/08/27 16:34:00, 0] nmbd/nmbd_nameregister.c:(73)
register_name_response: Answer
2018 Jan 16
0
idmap limit?
On Tue, 16 Jan 2018 16:20:52 +0100
Andreas Hauffe via samba <samba at lists.samba.org> wrote:
> Hi,
>
> no, that's my fault. I changed the UIDs and user names in my "ls -l"
> to unpersonalized/example data for my mail and didn't think about
> putting these values into the range. A better unpersonalized data
> example would look like:
>
>
2018 Jan 16
0
idmap limit?
On Tue, 16 Jan 2018 15:22:44 +0100
Andreas Hauffe via samba <samba at lists.samba.org> wrote:
> Hi,
>
> we are running a file server as member server of a windows 2012
> domain. Now we are facing the problem, that some UIDs are not mapped
> to the user names by the running winbindd process. This results in
> "nobody" usernames for nfs shares mounted by other
2012 Jan 15
1
idmap config doesn't allow range to be changed?
Hi there
I've just upgraded a working samba-3.5.8 CentOS-4.9 (yes - pretty old)
server to samba-3.6.1 and can't change "idmap config". We almost
immediately had issues with it not working for some users - and the logs
showed we'd run out of idmap mappings (strange that never happened
before with the older version...)
Anyway, I edited smb.conf so that
idmap config
2018 Jan 19
0
idmap limit?
Hi Andreas,
i'm sorry to jump on your thread as i can't really help you here.
But as i have to setup an AD subdomain of a parent domain with the same
requirements as yours apparently (aka parent domain managed by Windows
server holds users/groups accounts on a distant location but the compute
ressources and the GPO will be managed locally under a subdomain), i'm just
wondering if you
2009 Sep 01
2
Ignoring unknown parameter "idmap domains"
Dear
according this wiki
http://wiki.samba.org/index.php/Ldapsam_Editposix
i have enable EditPosix extension but i receive this error
Ignoring unknown parameter "idmap domains"
How can i fix it ?
Here it is my smb.conf :
[global]
workgroup = MSHOME
netbios name = PC-DTOUZEAU
server string = %h server
disable netbios =no
syslog = 3
log level = 10
log file = /var/log/samba/log.%m
2011 Aug 09
1
Ldapsam Editposix & idmap help required
Hi, I am more or less following this tutorial Ldapsam Editposix =
http://wiki.samba.org/index.php/Ldapsam_Editposix but can't quite get my
domain to work.
I think the issue is with the idmap part of the smb.conf but can't quite
figure out what's wrong with it or what the correct format should be.
My SMB.CONF file....
#interfaces = lo0 em0 127.0.0.1
bind interfaces only = no
2018 Jan 16
2
idmap limit?
Hi,
we are running a file server as member server of a windows 2012 domain.
Now we are facing the problem, that some UIDs are not mapped to the user
names by the running winbindd process. This results in "nobody"
usernames for nfs shares mounted by other clients.
When doing an "ls -l" in the homes directory on the member server (file
server), the list looks like:
2013 May 20
0
Samba 3.6 winbind issues
I've been using samba for several years now and so my configuration
hasnt changed much in that time. We've setup a samba pdc+ldap backend
and previously using smbldap-tools. I haven't had to add a new machine
in a long while until recently a new user said they couldn't remote
desktop to a windows server I have part of our domain. Older users
still were able to access it.
I decided