similar to: Password problems

Hi all, I have a class of Linux/OpenSource newbies and want to explain the origins of Samba as a typical Open Source project. My interest in Samba has grown, as well as my implementation of Samba. I started with 3 users on one server and now have ~2300 users in 10 buildings using Samba w/LDAP backend in a public school district. Anyway, I can give them my perspective, but I want them to know

Hello, I'm still trying to get this straightened out. I have the following system: System description RedHat 8.0 LDAP 2.1.23 Samba 3.0 I have basically 2 BDC that I want users to have home directories on. These also run LDAP backend as slave servers. Do all machines using the domain need to have machine accounts on the PDC or do some that use the BDC for home directories need to have

---------------------------- Original Message ---------------------------- Subject: Re: [Samba] posixAccount for Machines in LDAP? From: kent@www.warehamportal.mec.edu Date: Wed, July 14, 2004 12:19 pm To: "Paul Gienger" <pgienger@ae-solutions.com> -------------------------------------------------------------------------- Hi Paul, Finally got it to work. This is great!!

Stephanie, Thank you for your help. I tryed what you suggest but no luck.. I get this: root@lnxsrvr2:~# /usr/local/samba/bin/net groupmap add ntgroup="Domain Admins" unixgroup="Domain Admins" rid=512 Can't lookup UNIX group Domain Admins Is there something with initial compiling samba 3.0.0 that would disable this? All the documentation that I've seen makes it look so

Do I need to use winbind between pdc and bdc if I'm using LDAP backend? I have a PDC setup with LDAP master on backend and a BDC with slave LDAP in another building.I'm just having a problem with getting users to authenticate and use the BDC for home directories and exactly how to have W2k clients join the domain.. The BDC is in another building (connected by a slow connection) so it needs

Hello, I found an interesting thing that I don't know if it is a bug, by design or I need to be doing something that I'm not but here goes. My system RedHat 8.0 (1) PDC with LDAP 2.1.23 backend master, (3) BDC with LDAP slave backend. All are Samba 3.0.

Hello, I can't get my BDC to talk to the LDAP slave running on the same machine. Replication between slave and master works but samba on the BDC doesn't appear to be communicating with the slave LDAP server. Everything off the PDC works fine. -- smb.conf on BDC -- [global] workgroup = WarehamPS encrypt passwords = Yes time offset = 60 time server = Yes

Hello, I thought I had this all figured out but I don't. I have a RedHat 8 system using LDAP 2.1.23 as backend to Samba 3.0.0. I wasn't able to get machines to join the domain so I used the debug option in slapd -d 10 to see what Samba was sending the LDAP server. It looked like it was resolving my admin to the guest account. I went back to check groupmap list and got the following error

Not related to joining W2K clients to a domain but the "net" command refuses to work if there is a problem in smb.conf. Even if you run testparm and nothing is wrong. I don't kno if it's the order or whitespaces that causes it to not work. I"ve had to swap out smb.conf several times because I couldn't find the problem why the "net" command wouldn't run.

Hello, I'm trying to get Winbind to authenticate users that don't have local accounts on a SAMBA BDC. I have (3) BDCs (1) PDC running OpenLDAP 2.1.23 pass backend and Samba 3.0. These are on RedHat 8.0 systems. 3 BDC are also slave LDAP and 1 master directory server on the PDC. I went through the Samba documentation CH21 and made modifications to the BDCs and PDC as follows:

Hello, It's me again. I'm running Samba 3.0 and LDAP 2.1.23 on a RedHat 8.0 system. I am able to browse shares and home directories. I get a: Logon failure: unknown username or bad password when I try to connect a W2k machine. For Win/95/98 the system already works. I believe it is setup OK I need to work on scripts that work with MMC. I just want a basic connect a w2k machine right

I have yet to get group mapping to work in samba 3.0. Getting very frustrated. I'm using openldap 2.1.23 as the backend database for samba 3.0.0. I've added the base domain groups as posixAccounts to the LDAP database using smbldap-populate.pl. root@lnxsrvr2:/usr/local/etc/openldap# ldapsearch -xv -b "o=30greatneck,dc=home,dc=net" # Administrator, Users, 30GreatNeck, home.net

Hello, Having a problem with trust accounts failing after creation. The following is the system that I'm running Samba on: Fedora Core 2 (compiled from source) Samba 3.0.11 OpenLDAP 2.2.23 BerkeleyDB 4.3.27 Windows 2000 client machine I have a script to add machine trust accounts to LDAP. The first part adds a posix Account and attributes to LDAP, the second uses smbpasswd to add the Samba

I posted this earlier, but never saw it show up in the mailing list so I'm posting it again. I have a Samba 3.0 PDC using LDAP as it's password database backend, but I can't get a user to log on to a Win2k machine on the domain. In the log file for the PC (on the Samba machine), I see that the user is found in the LDAP backend but that getpwnam failed. The username does not

This is just a quick question, what is the difference between "+" and "@" when using groups for say valid users or write list ex valid users = +staff valid users = @staff -- Kent L. Nasveschuk <kent@wareham.k12.ma.us>

I'm in the middle of Samba 3.0.9 ==> 3.0.14a migration testing. Because I'm using newer tools, I am also using a newer verions of the Samba LDAP Tools. My older version, 0.8.4, used the 'mkntpwd' utility to generate NT passwords. The new version, 0.9.1 defaults to using (what looks like) a Perl module called Crypt::SmbHash. My questions: Do I need to continue to use mkntpwd?

Hello, I have a problem where non-AD systems can no longer connect to Samba shares. Samba 3.5.x servers are a members in AD, Windows 2008R2. This has worked flawlessly since we initiated it a couple years back. This happened to all 3 Samba servers after AD servers were rebooted. My thoughts are it was a Windows update that wrecked the system. Here is a typical setup: Winbind not used Samba

I remain unclear regarding Samba and LDAP. It appears that mkntpwd is required to generate a viable sambaNTPassword and sambaLMPassword attribute values. But I believe I read that the current incarnation of smbpasswd can accomplish this. Lastly, when utilzing phpLDAPadmin, do the NT and LM password fields contain the values generated by mkntpwd? -- Raymond

Hi. When I tried to setup my LDAP I used the smbldap-tools from idealx. I discovered some errors which made the tools unusable for me. Here's a fix for the bugs I discovered: a) I decided to use a suffix in the LDAP which contains spaces, ie. I used something like "o=My Org,c=DE". Because the suffix wasn't quoted in the various calls in the tools, this didn't work. b) It

I'm pleased to announce the release of the "arsenal" package v3.0.0 on CRAN (https://cran.r-project.org/package=arsenal)! "arsenal" has experienced some major growth in the last few months, starting with the release of v2.0.0 in January. We tried to maintain backwards compatibility wherever possible, but had to eliminate it in some places. With that said, here's the