On Mon, Aug 18, 2008 at 4:50 PM, David Miller <[EMAIL PROTECTED]> wrote:
> We've had good luck with this approach:
> http://blog.scottlowe.org/2007/01/15/linux-ad-integration-version-4/
>
> Basically using the Windows 2003 R2 schema extensions (as opposed to SFU)
> and Identity Management for Unix
We've had good luck with this approach:
http://blog.scottlowe.org/2007/01/15/linux-ad-integration-version-4/
Basically using the Windows 2003 R2 schema extensions (as opposed to SFU)
and Identity Management for Unix mmc.
On Mon, Aug 18, 2008 at 4:17 PM, BlackHand <
[EMAIL PROTECTED]> wrote:
> n
nate wrote:
Rob Townley wrote:
Over the weekend i gave up on CentOS and tried Fedora because Fedora
repositories have SaMBa 3.2, but CentOS only has 3.0. SaMBa 3.2 supports
sasl sign and seal (hashing and encryption) and supports NTLMv2 better and
using winbind with ADS.
Rebuild the samba s
Rob Townley wrote:
> Over the weekend i gave up on CentOS and tried Fedora because Fedora
> repositories have SaMBa 3.2, but CentOS only has 3.0. SaMBa 3.2 supports
> sasl sign and seal (hashing and encryption) and supports NTLMv2 better and
> using winbind with ADS.
Rebuild the samba src rpms
Sharing my experience with SSO of Linux clients to Active Directory.
Over the last 2 years or so, i had a great deal of trouble getting and
_keeping_ authentication to our Win2000/Win2003 Active Directory system
working from OpenSUSE and CentOS clients. ADS authentication would work
until reboot,
5 matches
Mail list logo
