similar to: interdomain trust relationships

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

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 -

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

I have two SAMBA PDC's with an OpenLDAP backend. My goal is to establish an interdomain trust between the two domains so that users from each backend can login to Windows systems by specifying accounts from either domain. I've followed the steps to establish the trusts and I can see accounts and groups using wbinfo and getent. I can access resources/shares from each domain but I'm

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 trying to set up samba server that trusts the local NT domain, so users who are logged intot the domain to not need to re-authenticate, nor have unix accounts set up. Config snipit: [global] workgroup = DC2DEV3 server string = DC2DEV3 netbios name = DC2DEV3 interfaces = en0 bind interfaces only = Yes smb passwd file =

I'm having an issue establishing a trust between a samba/ldap PDC and a windows 2003 Active directory server on a seperate domain. Here is what I've done. I've created a 2 way trust in windows with the samba domain. When I try to verify the outgoing trust from windows I get an access denied message. In samba logs I get " get_md4pw: Workstation CATS$: no account in domain"

Hi all I have two samba PDC installed according to these specifications: domain FOOBAR with pdc server name: BAR (ip 192.168.1.1) opensuse 11.1 samba-3.5.6-15.1 openldap2-2.4.12-5.6.1 smbldap-tools-0.9.5-25.1 A winxp called USUARIO1 joined to the FOOBAR domain (ip 192.168.1.100) domain LAPAZ with pdc server name: SERVERLPZ (ip 192.168.10.4) openSUSE 12.2 samba-3.6.7-48.12.1.i586

Hi, In trying to establish a trust relationship between a samba server (linux trusting domain) and WINNT (trusted domain, asnt01), an error occurred when the following command was executed, any suggestions please ?? bash> net rpc trustdom establish asnt01 >Password: >Could not connect to server ASNT1 >[2004/11/03 17:43:37, 0] rpc_parse/parse_prs.c:prs_mem_get(530) > prs_mem_get:

Hello, With the release of samba 3.0 I was vey excited with the new features and decided to experiment with it. I set my server up as a pdc which I am still working out some of the bugs but all and all I have it going and have a windows 2000 pro client join the domain and login and out very easy. The one problem is that before I roll this out to my other comptuers I need to change the policy on

Mother always told me that there'd be days like this. She just didn't tell me that they go on for weeks. OK - John's book suggests that we're not complete in this arena here...Yeah, I bought the Samba 3 How-to-guide - Borders/Phoenix had 3 on the shelf (now 2) - and also an LDAP book for reference. It's been a fun weekend ;-) problemo... # smbpasswd -x -i MULLEN

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

On Tue, August 5, 2008 8:12 pm, Michael Heydon wrote: > This is what happens when you rename a user, it is the same in XP and probably 2k as well. The only way that I know of to really change a No, this does not happen on Windows 2000. Note that I'm still running Windows 2000 because it runs very nicely under virtualization with only 256 MB allocated to the VM. ;) -- For a good laugh,