similar to: LDAP, tdbsam, and profiles

I would like to be able to change between backends but I'm worried that my users will encounter trouble loggin in. So I'm looking for reassurance that my command is ok. My current configuration is: passdb backend = ldapsam:ldap://10.10.10.10 smbpasswd guest I would like to change from ldap to tdbsam. Is this the command to use: # pdbedit -i ldapsam:ldap://10.10.10.10 -e tdbsam I

I need to migrate from samba w/LDAP 2.2.8a to 3.0.1pre3 with tdbsam. Any suggestions how to keep from having to change all the profiles? I have read through chapter 30 of the HOWTO but it assumes keeping the same backend. I need support to munge_dial and that is not available without mysql or tdbsam.... Thanks in advance for your help. Sean

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

Running Samba 3.x with tdbsam. Its a small nework of 4 Windwos XP machines. Having a little trouble adding the machines to the domain. pdbedit shows duplication machines names and such. Since its such a small number of machines, want to just start over with a fresh tdbsam as it seems faster then trying to clean it up. Can we just delete the existing tdbsam? Stop and restart Samba and

Hi All, I just added three users to my tdbsam with "pdbedit -a -u username" (had to do "useradd" first). All three appeared in tdbsam as they should, as verified with "pdbedit -L". But, all three also appeared in /etc/samba/smbpasswd. This is not a mistake, they were not there before. Are "tdbsam" and "smbpasswd" linked? I am confused.

Firstly I apologise for the length of this query but I am hoping that if I document everything I did someone might respond / be able to help. My Configuration is Samba 3.0.2a as a PDC on Redhat 8. I cannot for the life of me get the "Domain Admins" functionality to work I am hoping that another set of eyes can shed some light on this problem as I have now spent 41 hrs googling /

Hi there, I'm trying to import a smbpasswd-file into a Samba 3.0 installation on Debian Sarge using tdbsam as sole passdb backend. Copying pdbedit's documentation I used pdbedit -i smbpasswd:/root/smbpasswd.old The error message returned was tdb_update_sam: Failing to store a SAM_ACCOUNT for [foo] without a primary group RID where foo is the username to be imported. This message was

Hi list At the momtent I use samba as a pdc with tdbsam as passwd backend. I plan to use ldap and I already tried it out. Unfortunately I didn't find a way to disable roaming profiles. I used the smbldap tools. First there is the question if I should use add user script = /usr/sbin/smbldap-useradd -m "%u" with the -a (is a Windows User) option. If I don't, then windows account

As some of you may know, I'm trying to set up Samba BDC on a disk- and fan-less tiny mipsel_CPU router running OpenWRT distribution. I already managed to compile Samba 3.0.21a and OpenLDAP 2.3.18 for it, and they seem to work fine. The problem is, this tiny distribution for routers doesn't seem to have anything like Name Service Switch (NSS), and relies solely on /etc/passwd and

Hello people! I'd like to know about a practical guide which helps to migrate users from a perfect working Samba PDC running with tdbsam backend to a new backend to LDAP. Does "pdbedit -i xxx -e xxx" make all the job? My network is growing and I need a directory service to help find people so I'd like to see a LDAP server running well with Samba without rebuild my user

Who wins the fight for the roaming profile path, "logon path" in smb.conf or "profile path" set by pdbedit? How do you force the "profile path" in pdbedit to get its value from "logon path" in smb.conf? Is it possible to disable roaming profiles by user with pdbedit and leave "logon path" set in smb.conf? Thanks.

Hello everyone, I've been wondering if NT and UNIX username mapping can be done directly via the SAM database instead of the 'username map = <filename>' option in smb.conf. The problem with 'username map' files is that the mappings seem to work only in one direction, namely from NT towards UNIX usernames. However, I'd like to achieve a true, bi-directional

Dumb question time; I can't find the answer in the Samba-3 or HOWTO docs: how do you add users to the passdb.tdb (tdbsam's db)? Is pdbedit the only way? I ask because the Chapt 3 Samba-3 example has passdb = tdbsam in the samba config file, but the instructions for adding users are to use useradd and smbpasswd, which leave passdb.tdb empty (except for root--I have no idea how that

I'm having trouble setting the Workstations value on a tdbsam backend using pdbedit. I can't seem to find the correct syntax to accomplish this. I found some references in an older version of the HOWTO where there existed "Chapter 10. Account Information Databases". This whole chapter is missing from the current HOWTO even though it is referenced in the newest version (a

System: Sid ; Samba 3.0.0 ; using tdbsam ; no problems Goal: Would like to move password, group, and user data to ldap backend. Problem: I've read Samba-HOWTO-Collection.pdf and don't see exactly how to do this as the Howto addresses primarily the password backend. What I've done so far: 1) Created the openldap bdb and the dc=domain,dc=com base and the admin with password. 2) Run

Dear Samba Team, I have recently upgraded from Samba 2.2.8a to Samba 3.0.2 where I first noticed the issue. I have also installed 3.0.2a to check if the problem I found may have already been fixed before submitting this issue. Here's the problem: After migrating and switching from passdb backend "smbpasswd" to the new "tdbsam" backend, I started having problems with

I have Samba PDC and use tdbsam backend. I use the version 3.0.11, but recently I have exchanged it for the version 3.0.23c. Now I have a number of problem. Here is one of then. I wish to move one user "gad" from Domain Users (RID 513) to Domain Guests (RID 514). Now Primary group of user "gad" is "Domain Users": pdbedit -Lv gad -d0 Unix username: gad NT

Greetings, I am running samba-3.0.10-1.4E.9 installed from rpm on CentOS 4.4. I have it configured as a PDC. It is using the /passdb backend = tdbsam/ backend. I am using /pdbedit/ to make some configuration changes to user passwords. I would like to expire a users password, so that they are required to change it the next time they log in. From all that I have read in on-line resources

Hello! Rowland Penny via samba <samba at lists.samba.org> schrieb am 01.10.16 um 22:11:22 Uhr: > > when I do a pdbedit -a -u andreas where is the result > > stored? > > > > In whatever Samba database you have set in smb.conf This is the global part of smb.conf, its the standard part of a fresh openSUSE installation: [global] workgroup = WORKGROUP

I currently have a pure samba domain running off a Suse 9.1 machine. When I installed this domain I wasn't really comfortable with linux or LDAP so I used a tdbsam password file, and as there are only 30 or so users it seemed the way to go in the small amount of time I had available. Well, now I want to add a BDC to the mix I find I need to move to an LDAP backend. I only have two boxes at