similar to: samba3: problem with machine accounts - change PC name

Hi, I've a samba-3.0.2a running perfectly on redhat-8. Filesystem is EXT3 with ACL support. I can't upgrade the PDC to 3.0.3 or 3.0.4, because shares are only read-only. In 3.0.3 only home share and temp share are writable. All other shares are in read-only mode. Users can see the files/directories, but can't save anything or create new items. When trying to create a new item -

Hi, I want to achieve, that the IT staff could add machines (2000/XP) to samba-3 (LDAP backend) on the fly. Creating a new machine account to LDAP requires special access to samba (uid=0). In samba-2.2.x was a great parameter called "domain admin group". So everyone, who belonged to the specified group and root (uid=0) could modify LDAP. Others got message - "cannot access LDAP

> -----Original Message----- > From: G?mes G?za [mailto:geza@kzsdabas.sulinet.hu] > > I've configured for testing pruposes an other PDC with tdbsam backend, > and found, that with this backend win9x clients could get > user and group > list, while with ldapsam I had no success in it. Quite strange in my > opinion:-( Same problem here too. In 9x the userlist is

Hi, Could someone explain, why was parameter "domain admin group" removed from samba3? passdb/pdb_ldap got totally rewritten... but why remove an useful variable... # Removed Parameters (order alphabetically): # * domain admin group In 2.2.8 (with LDAP backend) I defined domain admin group = @"Domain Admins" and added several users to that group for creating machine

Hi, In smbldap-useradd.pl is a pice of code, which find the first unused uid starting from $UID_START (for example 1000). if (!defined($userUidNumber)) { # find first unused uid starting from $UID_START while (defined(getpwuid($UID_START))) { $UID_START++; } I've over 500 UID's in use (maximum UID is 1547). It works well, until you delete an user. After deleting an user,

> -----Original Message----- > From: Andrew Bartlett [mailto:abartlet@samba.org] > > passdb backend = ldapsam:"ldaps://ldap1 ldaps://ldap2" > is what you want. This helped me a little bit forward. I suggest to add this line also to samba-pdc help. But still I ran into problems. I fixed the passdb lines on PDC and BDC. If the second server (on PDC slave-ldap and on BDC

Hi, Samba-3 with LDAP backend is capable in this. I'm using it and it works. All you have to do, is to use LDAP and set proper account policies: $ pdbedit -P "bad lockout attempt" -C 5 (after 5 wrong password, user account will be locked out - samba sets password hashes to ***NOPASSWORD*** and user is unable to logon). $ pdbedit -P "min password length" -C 9 # password

Howdi, I can't add a w2k workstation to samba3 domain with my username. If I add my username to "admin users" list, then I can add the box to domain (but overritten by euid). My goal is, that joining domain can be done without using "admin users" option. Groupmapping is done and works. When machine is in domain and log in, I get full admin rights on that box. Removing the

This problem is something about SAMBA smbd. It doesn't matter whether samba runs also as WINS server. I wrote earlier: http://lists.samba.org/archive/samba/2003-December/077722.html My networks WINS server is WINDOWS 2000, not samba. I had both my PDC and BDC upgraded to 3.0.1 once. The errors accessing W2K workstation went away after downgrading both samba servers to 3.0.0. Even BDC can

Hi, I want to get my SAMBA-3.0.0 domain to trust W2K AD (mixed mode) both ways. I don't want to make my samba box an AD member, just trust it. Samba-PDC uses ldap as passdb. winbind isn't used. WINS server is running in W2K PDC server. Also created a machine account entry to LDAP base, set samba I flag. Here we go (using mmc @ w2k PDC): I add my samba domain to "Domains trusted by

Hi, I upgraded my 3.0.0 setup to 3.0.1. Basic functions worked well: logging to domain, login script executes, home drive gets connected, PDC is browseable, shares accessible. Network WINS server is a Win 2000 server, not samba PDC. First problem appeared, when users tried to open their Outlook mailbox'es to exchange 5.5 (on win 2000 server). Some users got into their mailbox, others

Hi, In samba help: samba-bdc.html there is a section available configs: Possible PDC/BDC plus LDAP configurations include: PDC -> LDAP master, with secondary slave LDAP server. BDC -> LDAP slave server, with secondary master LDAP server. So I configured it so and tested samba's ability to switch over to backup LDAP backend. If both LDAP servers are up, everything is just fine. But

Below is the topic list for the latest digest form of the mailing list. See if you can pick out the real messages from the myriad of warnings. :-( Today's Topics: 1. Autoreply to Thank you! (helpdesk@cdfreaks.com) 2. Symantec AVF detected an unrepairable virus in a message you sent (Administrator@fai.ie) 3. Re: Runaway SMBD process (Gerald (Jerry) Carter) 4. Re: Your

Hi I have figured out what went wrong. I have previously complied samba without ldap support. There are tdb files in /var/db/samba. I have just uninstall samba and remove all tdb files (this instruction was given when run make deinstall in the samba3 ports, but I didn't follow it before). I did a fresh recompile with ldap support and now the problem is gone. Thanks Patrick --- Patrick

add to each share writeable = yes or read-only = no This Helps! Rauno -----Original Message----- From: werner maes [mailto:werner.maes@cc.kuleuven.ac.be] Sent: 11. mai 2004. a. 16:19 To: samba@samba.org Subject: [Samba] BUG: Vfs audit module & samba 3.0.4 ==> share unaccessible Hello Maybe there's a bug in samba-3.0.4. The following configuration does NO longer work. It did

Robert, First off, the Samba Technical mailing list is not a help facility. Its purpose is purely for discussion of samba design and code implementation issues. Please confine your email to the normal Samba list. There are several avenues for Samba support: 1. The official documentation that consists of: Samba-3 by Example - a book that provides detailed deployment gudiance The Official

Well... It worked for me. Only thing I had to do was to add writeable = yes for each share. IMHO there is a slight difference since 3.0.3, not 1.9 ;) It would be nice to mention it in changelog too. Rauno -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Jeff Umbach wrote: | They changed the read only default to "yes" in | versions 3.0.3 and 3.0.4.

There are many discussions about this problem, but none of the developers of samba stepped in and gave any good explanation. Is this solved in Samba3.0.0 official release? (In what's new section of 3.0.0rc4, the 14th point is win2k3 security settings related matter. Is this the fix for SMB signature?) In one of the discussions there is a mention of disabling security option of Digitally

hi, I ran also into the home share problem, as discussed earlier in this list (http://lists.samba.org/archive/samba/2004-February/080593.html). But so far I haven't seen any solution. In samba 3.0.2 changelog is a line: "BUG 977: Don't create a homes share for a user if a static share already exists by the same name." I don't know what was changed, but it affected the

Hi, -----Original Message----- From: John H Terpstra [mailto:jht@samba.org] > "domain admin group" removed > > Because you now have something much more powerful that provides real NT > Groups to your NT/200x/XP clients. But if I use LDAP for both Samba and system auth. The groups, what I added with base.ldif (idealx) exist in samba and system. for example "getent