similar to: multiple passdb backends: ldaps for users, everything else locally?

Hi, i (naively) would like to have local AND ldap users (and groups...) on my standalone fileserver (security = user). "passdb backend = ldapsam" already works OK and i found some old posts on the internet about "chaining" passdb backends. so i tried "chaining" ldapsam and tdbsam, but although testparm doesn't complain and i can add local users with

How does the speed of SQL compare to the speed of LDAP? If the speeds are comparable, why bother with LDAP, which doesn't handle writes very well? Jim C. -- ----------------------------------------------------------------- | I can be reached on the following Instant Messenger services: | |---------------------------------------------------------------| | MSN: j_c_llings@hotmail.com AIM:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, We are discussing removing the capability to chaining passdb backends. It's a decent idea but overly complicates things IMO and unless it has wide spread use, we'll probably axe it soon (voting is starting up on the samba-tecnnical ml now). To give you an example of what I mean, is anyone using something like: passdb backend =

Dear List Members We are trying to setup samba PDC with tdbsam backend. First question: When "Home Directory" is not set in tdbsam does samba just use the setting of "logon home" in smb.conf? And when it's set does it ignore the smb.conf setting? Second question: Does tdbsam allow the inclusion of variables such as %a, %u, %H, etc.? We were looking at the "Big

I didn't get any answers so I try again: I am using tdbsam as passdb backand. I have added root user with pdbedit. The machine trust account was added on the fly. I have added the user with pdbedit. I have created the user in /etc/passwd. When the user logs in from a W2k and mounts the home-directory I noticed that Samba didn't take the home-directory information from tdbsam, it

Hello people, and thanks for this list :) I have a problem with samba, but first let me tell you the overall thing. I want to migrate my win2k print server to a Samba3 one ;) My willing is to make this print server available for our domain users. Thus, I decided to use these global settings security = server server = myPDCServer My problem is that I can't make it work, all I get is an

I'm using Samba marked 2.999+3.0cvs20020723 from Debian `sid'. In smb.conf, I've got: passdb backend = ldapsam:ldaps://master.ldap.server ldapsam:ldaps://backup.ldap.server tdbsam All works fine when both ldap servers are up, or when at least the first is up. When the first is down, though, samba tries to connect to it, doesn't manage to, and gives up instead of trying the

Hello, I'm a bit unclear about domain control with Samba3 and windows terminal server. I would like to have a samba PDC + shares for roaming terminal server profiles (W2K). I'm trying now with tdbsam backend ; after that I will try with ldap. With pdbedit I can modify the roaming profile path, but I can't modify the terminal server profile path ? Has anybody tried this

Hello, I have a question about machine accounts. I using Samba 3.0, OpenLDAP 2.1.30 and Berkeley 4.2.52 on backend on RedHat machines. I also have 3 slave/BDC's and 1 master/PDC Right now all of my users and groups exist entirely in the LDAP directory. I have a few accounts in addition to the normal system accounts that are used for emergency access. All authention and group enumeration uses

Hi, I got the following setup. I got a openLDAP server. This server is the master server for LDAP functions. I named this ldapsrv. I got a samba server with openLDAP install on it as well. This LDAP server is the slave to ldapsrv. I named this sambasrv. The sambasrv currently have the following setup in /etc/smb.conf:- passdb backend = ldapsam:ldap://ldapsrv.domain idmap backend =

Hello I would like to use plaintext backend with a simple Samba 3.0.6 configuration to get rid of the system of double passwords and rely just on the plain old unix /etc/passwd ones. However I couldn't find any information about it in 1) man smb.conf 2) online Samba official HOWTO I tried putting passdb backend = plaintext into a smb.conf file with security=share and the Samba server

I have tried everything that I know of. I have reviewed the services file and the swat file in xinetd.d a tun of times. It appears, via netstat that swat is listening on port 901. However when I attempt to access it via the Mozilla browser on my Fedora server (with 127.0.0.1:901 or localhost:901) nothing happens. It just sits there. However, if I access it via webmin (which has swat stored

hi, it's me again =) i'm using openldap v2.2 and samba v3(.0.4) i wonder, if i don't use winbind, do i really need the parameter "idmap backend = " in smb.conf on PDCs/BDCs ??? those machines find their SID/UID/GID via "passdb backend =" don't they? thx -- "Matrix - more than a vision"

The Samba 3.0.5rc1 server is configured as a PDC. [global] # client code page = 866 # NetBIOS name of that comp netbios name = TOLTEC #Name of Domain workgroup = liin #Comment server string = Samba PDC %v #Interface where samba works interfaces = 10.0.0.4/24 127.0.0.1/24 bind interfaces only = yes hosts allow = 10.0.0. name resolve

Hi Rowland, > If you mean 'can I set up samba 4 as an AD DC with an LDAP backend > instead of the builtin LDAP server' then the answer is no. does samba 4 works with external LDAP server if it isn't working as AD DC? I'm a bit confused because I want to update from samba 3 to 4 and using our internal LDAP server to authenticate the users. cu - Bernd

We're in the midst of setting up a Samba 3 system as our PDC. I come from a Samba 2 world, where the passdb backend was smbpasswd. What's the ... er, 'best' passdb backend at this point? To qualify best, there's no limitations on the type of storage used (LDAP, MySQL, XML, etc). I'm just looking for something that's going to make integration with a 2000/XP domain

Hello all, I have downloaded samba-2.2.8a-1-sol8-suncc-32bit.pkg.gz and I am trying to gunzip it but I get gunzip: samba-2.2.8a-1-sol8-gcc295.pkg.gz: not in gzip format what could be the problem ? ********************************************************************************* Ce courriel ainsi que ses pieces jointes sont strictement reserves a l'usage de la ou du destinataire et peut

Hi, I was having problem with the tdbsam backend in which a particular user got listed twice with pdbedit. (http://www.mail-archive.com/samba at lists.samba.org/msg109110.html) Without much hope in fixing it, I am planning to re-generating passdb.tdb on my PDC by: (1)exporting tdbsam to smbpasswd backend (2)delete passdb.tdb (3)re-import smbpasswd to tdbsam backend With the command `

dear list members how can i restrict access to samba with the "hosts allow" configuration for only part of a subnet without having to list all the individual ip-numbers? e.g. we have the subnet 123.123.123.1 - 123.123.123.512 and i would like that only the hosts with the ip numbers between 123.123.123.237-123.123.123.319 have access. how can i do this? all hostnames have the

Hallo, I'm trying to convert smbpasswd to passdb.tdb. cd /etc/samba/private # (where smbpasswd lies) pdbedit -i smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb converts all human users, but it converts (or transfers) no machine account. In "smbpasswd" are many entries beginning with (p.e.) mac001$ for these accounts, pdbedit -L -v | grep -i mac shows