Just when I thought I had idmap changes correct for 3.6, I realize I
have a setup that's not quite right:
getent passwd
-No AD users
getent passwd DOMAINA\\aduser
aduser:*:1001601:1000513::/home/aduser:/bin/bash
Shouldn't getent passwd show both local and AD users?
Samba has had such an
compat
group_compat nis
hostsfiles dns
netgroup files [notfound=return] nis
passwd compat
passwd_compatnis
On 09/29/2012 05:03 AM, David Touzeau wrote:
Thanks Heather Choi
But in my nsswitch i
You definitely should have files placed *before* winbind of passwd,
group and shadow, like:
passwd: files winbind
shadow: files winbind
group: files winbind
Otherwise, you will be hitting AD a whole ton for localized users and
definitely root with services running.
On
Looks like you have a potentially conflicting idmap block here:
idmap backend = rid:DOMAN=1-2
and here:
idmap uid = 1-2
idmap gid = 1-2
This is more contemporary with Samba 3.6:
idmap config * : backend = tdb
idmap config * : range = 20001-3
idmap config
samba3x is essentially anything beyond the original Samba 3.0 packages.
However, the fact they didn't bump samba3x is actually not true. Redhat
started doing this with RHEL5.4 as a technology preview with Samba 3.3:
I noticed you tried to comment out the default idmap section. The range
also starts very low, (too low). I think you might be running into
uid/gid collisions because of that.
Something like this is more preferrable (in addition to setting your
ranges):
idmap config * : backend = tdb
You really shouldn't bother trying to compile Samba by hand.
If you want Samba 3.4, get this:
http://ftp.sernet.de/pub/samba/3.4/rhel/6/x86_64/
On 07/13/2012 03:51 AM, Jonathan Buzzard wrote:
On 13/07/12 02:36, Heather Choi wrote:
How is Samba 3.6 against ADS broken? I have Samba 3.6.6
I think you might be missing some stuff in the prior config you had.
The following works for me with Samba 3.6.6:
idmap config * : backend = tdb
idmap config * : range = 100-199
idmap config MYDOMAIN : backend = rid
idmap config MYDOMAIN : range = 1000-99
idmap
How is Samba 3.6 against ADS broken? I have Samba 3.6.6 on SL6.2 with
ADS and it's running great...
In fact on my Windows 7 laptop, with my SSH client, I can SSH in with
kerberos, no password entering is needed. :-)Same with Linux to Linux.
If you really have to install Samba 3.4 against
If you configure PAM and kerberos properly, you do not need to do a
kinit first. I get them automatically when I login. They automatically
renew when I type my password into the GNOME screensaver.
Btw, I am also using Samba 3, not Samba4.
On 07/11/2012 03:07 AM, Quinn Plattel wrote:
Btw,
What is the lwopen idmap backend? First I've heard of that one:-)
Also, why are you setting your homedir template as /dev/null, and yet
shell as /bin/true? That's pretty goofy..=-O
On 07/10/2012 07:20 AM, velusamy Krishnan wrote:
Hi,
I have followed the all the steps given, in
I'm pretty sure that would be samba3x, not samba3 for RHEL/CentOS 5.
On 06/06/2012 09:07 AM, John Doe wrote:
From: Hoover, Tony hoo...@sal.ksu.edu
CentOS 5 does have a newer samba available. To get it:
yum remove samba
yum install samba3
or to get really fresh samba, use the SerNet repos.
In my smb.conf file, I currently I have a user share definition as:
[userdir]
path = /samba/%U
writeable = yes
The problem is, the user pool is in the tens of thousands, so it is not
practical to have that many directories within /samba.
I'd like to somehow dynamically configure the
13 matches
Mail list logo
