I've been able to make Samba 3.0 work using Security=domain, which is basically Samba 
2 "compatibility mode", but none of the AD specific functions work with the heimdal 
0.4e that comes with the
system.  I've managed to get heimdal 0.6 built, but the shared libraries seem to be 
incompatible with the client programs (ssh, etc.) built using 0.4.  I'm not up to 
rebuilding all of the products
that depend on heimdal.

I DO have a version of MIT Kerberos 5 that can coexist with heimdal, so that's next.  
I've been otherwise occupied this week.


> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
> Michael MacIsaac
> Sent: Thursday, October 23, 2003 10:04 AM
> To: [EMAIL PROTECTED]
> Subject: [LINUX-390] Samba3 RPM for SuSE or Red Hat?
>
>
> Hi list,
>
> I got Samba3 to build with the small code change that Ken
> Hall pointed out
> (warning: have at least 1.5GB free space - "make clean" will
> free most of
> it up after the build).  I got basic SMB shares working with
> the smbpasswd
> file (warning: it seems the "valid users = %S" in the homes
> section of the
> default SLES-8 smb.conf file breaks the homes shares).
>
> I then tried to join an Active Directory domain without success.  As I
> understand it, Samba3 looks like a Windows 2000+ member joining while
> Samba2 looks like an NT4 member (and thus requires the AD
> server to be in
> "mixed mode", aka "hybrid mode").  Ken and Lucius suggested
> MIT kerberos -
> I spent some time on this, but it seems too much like major
> surgery and
> almost certainly won't be supported by the distributors.
>
> Do any of the SuSE or Red Hat developers have their ears on?
> When will a
> Samba3 RPM be available?  Thanks.
>
>           -Mike MacIsaac, IBM  mikemac at us.ibm.com   (845) 433-7061
>

Reply via email to