[TriLUG] I'm in SAMBA hell

[Ryan Leathers]

I'm migrating services from Win2k to Linux.  The majority of my end
users are sticking with windows on their desktop PC's.  
I am in need of some sound advice in handling authentication of users
who "browse" SMB shares on Linux servers.

In my pilot, I have 3 Linux servers running SMB.  They are part of the
same workgroup/domain.  I am compelled to leave the existing domain
alone and build this new workgroup during the pilot.  I suppose it's
most correct to call it a workgroup since there are no NT or Win2k hosts
(no domain controllers).
Authentication is being handled per user.  End users have Win2k Pro on
their PC's and are generally logged in as members of another domain.  My
problems are: synchronization of credentials, visibility of Linux SMB
shares in browse lists on the Win2k hosts.  

My current plan: configure the Linux servers to point to one place for
credentials.  I will still have a credential conflict since users are
members of a domain and a workgroup.  They want to use a single set of
uid/passwd for both.  By setting the security=server option and picking
one of the Linux servers to be that server I hope to simplify my life.
At least this way the credentials will be consistent for all shares on
the Linux servers.  To aid in my quest for "browsability" I plan on
making the authentication server handle WINS chores and point the others
at it.      

Any thoughts ?

Ryan
-----Original Message-----
From: Jon Carnes [mailto:jonc at nc.rr.com]
Sent: Tuesday, September 24, 2002 7:53 AM
To: trilug at trilug.org
Subject: Re: [TriLUG] Suse releases exchange server clone ($999) no
client licenses

It's also worthy to note that this is now the cheapest drop-in
replacement for an Exchange server. It's 40% cheaper than the previous
Linux solution. This may not be a mile-stone for Open Source, but it is
certainly one for the evolution of Linux in the workplace.

Migrating folks off of proprietary MS solutions is made difficult by
their dependence on Exchange. If you remove the Exchange dependency then
you break the strongest lock that MS has on small and medium sized
businesses.

Also, this adds more competition into that market - which drops prices
and encourages better more responsive programming and services.  It's a
big deal for Linux to have these solutions available and actively being
developed. It's also a big deal to contractors (like me) who setup Linux
based services for folks - or even help them migrate off of MS products
over to cheaper Linux based solutions.

The next nice thing will be when LDAP (or some Directory Services) is
fully functional and supported with easy installations and
administration.

Jon Carnes

On Tue, 2002-09-24 at 08:43, Ben Pitzer wrote:
> Can this group ever get past the flame-bait distro bashing?  C'mon,
> folks, whatever your personal preference, other distros have redeeming
> qualities, too.  And while the Skyrix portion of this product may be
> closed source, it may be exactly what somebody needs to start to move
> towards Linux and an open source, non-Exchange clone groupware
platform.
>
> Regards,
> Ben Pitzer
>
> PS - Sorry to pick on you, Tom.  Nothing personal.  I've seen it, and
> thought about it before, and your post just reminded me that I wanted
to
> say something.
>
> > I looked at this product before they released, and the important
pieces
> > (Skyrix) are closed source, in typical SuSE fashion.
>
> _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html


_______________________________________________
TriLUG mailing list
    http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ:
    http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3061 bytes
Desc: not available
URL: <http://www.trilug.org/pipermail/trilug/attachments/20020924/24e1c907/attachment.bin>