similar to: different win machines on PDC not accessible at diffe rent times

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 -

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

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

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

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

ok, i noticed the gid of ldap group "users" was 539, but the one it was migrated from in /etc/group was 100, so I changed the gid and everything seems to work now? but why should it care that the gid is the same as it's /etc/group counterpart? --- On Tue 01/27, John H. < mrmailer@myway.com > wrote: From: John H. [mailto: mrmailer@myway.com] To: samba@lists.samba.org

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

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, Running samba 3.0.0, LDAP passdb. I've in smb.conf (script is from samba3.0.0 source tree) add machine script = /usr/local/sbin/smbldap-useradd.pl -w %u delete user script = /usr/local/sbin/smbldap-userdel.pl %u When a machine (win 2000/xp) is added once to samba domain on-the-fly. Everything works well. Things get tricky, when there's need to change machine name. Samba doesn't

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

the weirdness continues net groupmap modify ntgroup="Domain Admins" unixgroup="ntadmin" NT Group Domain Admins doesn't exist in mapping DB --- On Mon 01/26, John H. < mrmailer@myway.com > wrote: From: John H. [mailto: mrmailer@myway.com] To: samba@lists.samba.org Date: Mon, 26 Jan 2004 17:40:49 -0500 (EST) Subject: Re: [Samba] net:

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

well, they both have the same sid, for some bizarre reason. net groupmap list -s /etc/samba/smb.ldap |grep "Admin" Domain Admins (S-1-5-21-4070452498-3149834983-2923667569-512) -> 512 Administrators (S-1-5-21-4070452498-3149834983-2923667569-544) -> 544 Domain Admins (S-1-5-21-4070452498-3149834983-2923667569-512) -> ntadmin and see, it has a posixgroup entry? # LDIF Export

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

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

I am having nearly the EXACT same problem as http://lists.samba.org/archive/samba-technical/2003-December/033315.html I have samba 3.0.1-1 rpms and fedora core 1. Samba is set as a WINS server, which the win2k machines, who use DHCP from router, are pointed to by the WINS server address specified in router(each of the win2k machines, via ipconfig /all reveal they do in fact use the wins server).