Current Development Updates?

[Armand Welsh]

*This message was transferred with a trial version of CommuniGate(tm) Pro*
vendors usually freak out when you are doing something they know nothing
about.  I can't begin to tell you how many vendors insisted they had to have
windows NT4.0 or 2K for the application server.  After jumping though all
the hoops, it turned out they didn't have the terminology right.  They often
used the windows box a file server, from which the clients launch the client
application, which in turn, usually talked to a database back end, that,
more often than not, was either an MS-Access file, also stored on the
server, or an SQL type database server (usually Oracle, or MS-SQL, but most
any SQL server would work).  We would usually, replace the SQL server with
what we liked best, and move the files over to the samba server, after they
left, and all worked fine, for obvious reasons.

I know what you are talking about, in regards to full support, officially, I
believe they are shooting for full support in 3.0, by this, I mean, the
trusts should would.  2.2, will probably continue to function as it does
now, but you can't do sever trusted opperations that will be available in
3.0.  Perhaps we will get an OFFICIAL answer though.. :)

----- Original Message -----
From: "Scott Merrill" <smerrill at svfc.org>
To: <samba-ntdom at lists.samba.org>
Sent: Thursday, January 11, 2001 7:38 AM
Subject: Current Development Updates?


> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> I'm dealing with a software vendor who makes a Windows application that
> requires NT domain authentication.  They're a little dodgy about our use
of
> Samba for domain controllers, and I'd like to be able to provide some
> specific information to them about where things stand.
>
> This software vendor wants us to use Windows 2000 for their application
> server.  As I understand it, Samba can't adequately support a Windows 2000
> member server in the domain yet.  We don't need full group enumeration, or
> trust relationships, or any of that.  All I need is for a Windows 2000
> member server to be able to integrate into our domain (which has an even
> number of characters in its name!).
>
> http://us4.samba.org/samba/development.html suggests that Windows 2000
> domain integration won't happen until Samba 3.0.  But all the traffic on
> this list involves people getting the 2.2 CVS version to integrate with
> Windows 2000 servers.  Are we all jumping the gun with 2.2, or are the
Samba
> web pages slightly out of date in regards to proposed features for 2.2?
>
> I know there was a big brouhaha awhile back about getting more specific
> timelines.  I'm not after anything of the sort - I can patiently wait
until
> it's done.  I'm just looking to provide _correct_ development information
to
> my software vendor so that they can be a little more comfortable with our
> use of Samba.
>
> Thanks very much!
> Scott
>
>
>