similar to: ldapsam:trusted=yes

Displaying 20 results from an estimated 10000 matches similar to: "ldapsam:trusted=yes"

2006 Mar 24
0
Fwd: Re: Migrate NT domain 4 to samba
I tried "net lookup dc" and samba PDC did not show. The NT machine we have has been shut down and not functional anymore. Right now, we only have one linux box with gentoo running samba and we want it to be the PDC. Thanks, -Ivan >X-Original-To: iordonez@nature.berkeley.edu >Delivered-To: iordonez@nature.berkeley.edu >Subject: Re: [Samba] Migrate NT domain 4 to samba
2006 May 04
6
Share Access
Could someone help me understand if what I'm seeing with share access is correct? On my samba domain I have two users (user1 and user2) and one share; the share has attribute "writelist = user1". On a linux machine I: mount the share with "mount -t cifs -o username=user1" successfully open a file in the share for writing with the perl "open" function
2006 Aug 18
3
share write access
Hi, I am testing share parameters, and have the following share definition: ## Section - [shareA] [shareA] path = /tmp/shareA writelist = user1 and do not understand why user1 cannot write files in the share when connected as user1. Unix permissions for the share files are rw for everyone, and the share directory has wide-open permissions. Samba version is 3.0.20b-3.4-SUSE.
2006 Jul 20
1
guest ok
I have the following smb.conf file. Note the "guestaccount" parameter, and the guest parameters in shareA, shareB, and shareC. # # Generated by modify_samba_config.pl # [global] adminusers = Administrator, root logonhome = \\%L\%U\.9xprofile addsharecommand = /usr/local/autobench/sources/samba/util/modify_samba_config.pl
2005 Nov 07
0
Share file permissions
I have not been able to find this exact problem on the mailing list; apologize if I missed it. I have tried both samba versions 3.0.20 and 3.0.21pre1. The file share in smb.conf has these entries: path = /home/samba/myshare guest ok = no read only = no force create mode = 0644 force directory mode = 0775 The directory "myshare" has the following permissions:
2011 Jul 09
1
ldapsam:trusted=yes, 'user in passdb, but getpwnam() fails'
Hello all, I am working with samba-3.5.6 on Debian Squeeze. From the smb.conf(5), I assumed that, by using 'ldapsam:trusted=yes', one can avoid touching the NSS/PAM configuration. However, I am getting a: user in passdb, but getpwnam() fails in the logs. Is my assumption wrong? Regards, Joe -- .o. I'm a Free man. I use Free Software. ..o ooo http://www.joesteeve.org/
2005 Mar 22
1
Problem with "ldapsam:trusted = yes"
Hi, I updated from 3.0.11 to 3.0.12 and tried the new ldapsam:trusted parameter. Alas smbd dies silently a second after startup. With debug level 2 I can't see any reason in the logfile. My smb.conf is (relevant part I hope): ================================= [global] workgroup = BBS_XXX netbios aliases = fileserver revreselif passdb backend = ldapsam:ldap://localhost
2007 Mar 15
2
3.0.23 ldapsam:trusted=yes problem
Hi all! I've a running Samba PDC (LDAP backend) with windows clients. All the users are in the LDAP, including the 'guest' user. All except the 'root' user which is a regular user. Then change in the smb.conf ldapsam:trusted = yes ldapsam:editposix = yes and noticed some speed-up when listing groups, look file ownerships, and so on. But I can't add machines to the
2006 May 21
1
ldapsam:trusted = yes : trouble getting it to work
I have been trying for a while now to enable set the parameter ?ldapsam:trusted? to ?yes? in smb.conf but as soon as I enable it, users cannot access shares anymore. I am trying to enable this because the users are member of a lot of groups and I want to take the stress off the ldap server. I have searched the lists for previous posts with the same problem and I tried to figure out if it has been
2005 Sep 29
7
ldapsam:trusted = yes kills smbd
Hi, we want to use ldapsam:trusted=yes to improve performace as nss_ldap is killing our ldap server doing enumeration. once i enable it smbd dies silently... this is the last part of a ./smbd -d 10 -i NT user token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups smbldap_search: base => [ou=groups,ou=filestore,dc=sunderland,dc=ac,dc=uk], filt er =>
2007 Aug 23
1
Samba tuning - ldapsam:trusted
Hey everybody... I have a samba configured as PDC and LDAP installed in the same machine. Ok. Everything is working correctly, but I want to enhance the performance. So, I read that if I set the ldapsam:trusted option, samba will directly communicate to ldap to get informations (not using NSS anymore). So, I decided to put "ldapsam:trusted = yes" and "guest account = nobody"
2006 Oct 04
1
Samba 3.0.21 and after creates ldapsam:trusted display problems in User Manager?
I recently upgraded a 3.0.14a installation (using an OpenLDAP backend) to 3.0.23c and noticed that when using the Windows User Manager group members are no longer listed when viewing a group--when 'ldapsam:trusted = yes' is set. I've since compiled and tested various versions using default options and the last time I see this member listing working was in 3.0.20b--3.0.21 and
2010 May 02
1
How ot migrate from /etc/samba/smbpasswd -> LDAP ldapsam:trusted
Hi, has anyone done a migration from an "old" smb passwd file = /etc/samba/smbpasswd setup to a "up to date" LDAP ldapsam:trusted setting? (Centos 5.4, samba-3.0.33-3.28, openldap-2.3.43) If so, is there some how to? Or may somewone share his/her experience with me. Thanks a lot and best regards, G?tz -- G?tz Reinicke IT-Koordinator Tel. +49 7141 969 420 Fax +49 7141
2006 Jan 03
1
ldapsam:trusted work?
Samba 3.0.21(and 'a'), AIX 5.2. Was looking as what appears to be a fantastic optimization, but can't find info in source code or swat and turning the option on makes smbd do exit(-1) (on AIX anyway). ldapsam:trusted = yes Does this really exist? Does it need a maintainer? Are there any docs/source? Cheers, Bill
2006 Jun 28
0
samba with ldap and ldapsam:trusted possibly
Greetings Curious about a couple of things. In a group object, is it required, better or no effect to maintain the sambaSIDList attribute in a synchronized fashion with the memberUID (list) attribute. In other words keeping the two lists pointing to the same list of person objects?? Similarly are there any possible negative side effects if the sambaPrimaryGroupSID attribute in a person object
2019 Feb 05
0
Samba 4.7 and Editposix/Trusted Ldapsam extension support.
On Tue, 5 Feb 2019 11:56:05 +0300 Vladimir Skubriev <skubriev at cvisionlab.com> wrote: > вт, 5 февр. 2019 г. в 11:42, Rowland Penny via samba > <samba at lists.samba.org > >: > > > On Tue, 5 Feb 2019 11:31:53 +0300 > > Vladimir Skubriev via samba <samba at lists.samba.org> wrote: > > > > > Something like this. > > > > >
2019 Feb 05
3
Samba 4.7 and Editposix/Trusted Ldapsam extension support.
Is there a page with support status of this feature in current samba releases ? What is the current status and future? -- Best Regards, Vladimir Skubriev System Administrator CVisionLab +7.918.504.38.20 skubriev at cvisionlab.com http://cvisionlab.com
2019 Feb 05
3
Samba 4.7 and Editposix/Trusted Ldapsam extension support.
Something like this. But this link has no info that I need. On the roadmap: https://wiki.samba.org/index.php/Roadmap There is information <https://wiki.samba.org/index.php/Samba4/LDAP_Backend#.28De.29motivation> about general purpose LDAP server as the backend (e.g. openLDAP). But that's not what i was looking for. I looking for status of `passdb backend = ldapsam` feature. This
2006 Aug 22
0
3.0.23 PDC with ldapsam:trusted backend - failed to setup guest info.
Hi everybody. This is my first post here - Im hoping that someone out there can shed some light on my little problem, it's starting to drive me nuts! :) Ive had a look through the archives as well as other methods for finding a solution to my problem but to no avail, so I decided to post here - hope you dont mind! Im migrating an old samba 2.2 PDC to a new system running 3.0.23, we
2001 Nov 09
1
Fix to track-kameipv6 branch for socket.c
I ran into a problem where systems without DNS entries could not connect to the rsync server with the IPV6 patch applied. Here is a fix to the problem. Basically they were checking the list of IP addresses returned by getaddr even if getaddr failed. I just changed it so they only check the list of IP addresses if getaddr succeeds. Any comments on this please email me directly because I do not