I'm trying to do something fairly simple: login to a Linux box using a
Windows AD-based account. I've followed the various recipes available
online for configuring Linux (winbind, PAM, etc.) to this send, and I've
got it working ... almost.
I'm able to authenticate an AD-based user immediately
Adam Nielsen wrote:
password server = vmdc1.domain.local
AFAIK this option is only required for security = DOMAIN - if you're
using security = ADS then when you join the domain Samba/winbind will
find out which server to use for passwords.
Thanks for the reply, Adam. I believe
Vijay Avarachen wrote:
Try running just nmbd and winbind. WIthout nmbd running, wins resolution of
the linux host is not going to work and maybe that is what is hindering the
authentication.
Thanks for the reply, but running nmbd has no effect on the problem.
-McG
--
To unsubscribe from this
McGlorfin wrote:
I'm trying to do something fairly simple: login to a Linux box using a
Windows AD-based account. [...]
[...] Is this more likely to be a
misconfiguration or an issue with my version of Samba?
After upgrading to version 3.0.21a, my problems have disappeared. The
WHATSNEW
There's been a lot of good discussion so far re Wink3 R2, but not much
on actually using the RFC2207-compliant schema therein.
So is anybody using Samba to do authentication against AD in Win2k3 R2?
TIA,
McG
--
To unsubscribe from this list go to the following URL and read the
instructions:
eric roseme wrote:
I have not tried loading our POSIX ID's onto R2, but I doubt it will
work with Samba as-is because the attribute names have changed from SFU.
SFU pre-fixed the RFC2307 attributes with msSFU-30 (thus not following
the RFC) but R2 actually uses the correct attribute names.
Yanick Quirion wrote:
- I modified file /etc/nsswitch.conf as follow:
passwd: files ldap
shadow: files ldap
group: files ldap
In addition to what others have said, you should change ldap to
winbind in your nsswitch.conf.
You also need to make sure that you have defined uid/gid values for
