similar to: Samba3+Win9x userlist, Bug596?!

>Thereby sorry for being impolite :-(, but at present I'm running samba >3.0.1pre1 with ldapsam in the production servers, >and Win9x clients couldn't get list of users and groups from Samba DCs (Bug596). I have 3 >choices: >- -- Switch back to 2.2.7 (not very nice:-(, I would need group support for policy) >- -- Switch to tdbsam with fam/rsync/ssh-ing password and group

Hi ! I was just wondering if that piece of code was important (for security and such), because I had to comment it in smbldap.c before compiling samba-3.0; otherwise, I would have errors like: "(Insufficient access)smbldap_open: cannot access LDAP when not root" #ifndef NO_LDAP_SECURITY if (geteuid() != 0) { DEBUG(0, ("smbldap_open: cannot access LDAP

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, 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

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

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

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.

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

Hello, I am also triing to set up a interdomain relationship with a NT domain and I can't create the user, I execute the following command and I get this. smbpasswd -a -i xxx New SMB password: Retype new SMB password: Failed initialise SAM_ACCOUNT for user xxx$. Failed to modify password entry for user xxx$ I have samba set up so that I can set up users and machine automatically, so I am

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear List, Few days ago I've posted, that my Win9x boxes are unable to get the list of domain users and groups from samba-3.0.0 server (for details see bug 596). Unfortunately the same is true for samba-3.0.1pre1. Please people also having win9x boxes and Samba3 PDC confirm that it is a bug, or a configuration error. Thanks for any suggestion.

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

I've got a Samba 2.2.7a domain with an LDAP backend. It's been working for nearly 3 months now without much bother. By the way: Great work and thanks for all of the effort! I have been missing one minor thing from the setup since I moved away from NT 4: Password Expiration. In the past I have posted questions about this on the list and I've gotten two answers: "Wait for

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I'm on the way to implement samba with ldap on five servers (each owns a different nt-domain) and a master server which maintains the central user database which gets replicated to all the other servers. Now I have just one more problem, namely homedirs. I want every user to have a homedir to store for example his profile. This has to

> -----Original Message----- > From: jean-marc pouchoulon > [mailto:jean-marc.pouchoulon@ac-montpellier.fr] > Sent: mercredi 22 octobre 2003 14:54 > To: 'jean-marc pouchoulon'; samba@lists.samba.org > Cc: eric.jourdan@ac-montpellier.fr > Subject: RE : [Samba] Samba 3 pre01 security=domain problem to > accessfromxpclient > > > Just one more thing > With

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

I just installed Red Hat v. 6.2 and would like to configure SAMBA. I was wondering if you could point me to some good documentation sites that can lead me step by step through setup and configuration of SAMBA. I'll be experimenting with it in the meantime but your help will be extremely helpfull. Thank you, Jerry Lawson MCSE, MCP +Internet

I try to implement a new server using domain auth ( server , pdc , bdc are on redhat 9 samba3pre1) Smb.conf of server: [global] workgroup = DOMAIN netbios name = G4 server string = %h server (Samba %v) security = domain password server = SERV2 SERV3 (PDC and BDC) wins support = no wins proxy = no wins server =