Client for Samba Networks

[Ken Cobler]

Sean Elble wrote:

> The only problem with this idea is that it takes away from the point of what
> Samba is: a piece of software that makes a UNIX system look like a regular
> Windows NT/2000 server to a Windows client. If this were back in the day
> when things like Pathworks, Banyan, and LANtastic were still big, then it
> wouldn't be such a bad idea; all of those systems were, at least in part,
> based upon SMB. However, today, it is a different story: Samba was designed
> to ease the addition of a UNIX server in a Windows environment, especially
> when a Windows NT/2000 domain/AD structure is already in place. If you are
> setting up a network that consists solely of Samba servers, the idea is
> better, but that still leaves you with the hassle of dealing with the
> installation of a new network client, whereas the Client For Microsoft
> Networks is pre-installed in every Windows version.
>

I understand the direction Samba started with.  However, I think a Client for
Samba Networks could be incorporated to the current Samba project.  I administer
several locations that do have only Samba servers and MS Windows computers.
Especially with Windows 2000, and now Windows XP, integrating PDC functions into
Samba could be better handled by controlling the entire protocol and
implementation (both the client and server end).

I am not suggesting to abandon the current path, but, rather forking another
path for a Client for Samba Networks.  The Client for Samba Networks would not
fit all situations, just as, a complete PDC Domain oriented Client for MS
Networks does not best fit all Windows networks (sometimes it is too much
overhead).

Also, since the Client for Samba Networks would be GPLed, perhaps a port could
be made for Macintosh or other target client machines.

Ken Cobler