From: "Robert Comer" 

> No, that's not the reason. The code quality of Windows is irrelevant to
the
> incapability of Samba to get to a basically working state out of the box.
> (I'm interested to know what the 'half-baked' and 'spagetti' opinion is
> based on).

I agree with you on that, but MS has had a habit of changing the
authentication rules fairly often...

- Bob Comer


"Paul Ranson"  wrote in message
news:3de12d5e$1{at}w3.nls.net...
> No, that's not the reason. The code quality of Windows is irrelevant to
the
> incapability of Samba to get to a basically working state out of the box.
> (I'm interested to know what the 'half-baked' and 'spagetti' opinion is
> based on).
>
> Samba is trying to be all things to everybody, to operate at the most
> complex level of Windows networking. A level that's not applicable to the
> great majority of situations where one just wants to share files between a
> Windows box and a Unix box.
>
> Almost 10 years ago when I first came across it it 'just worked' with very
> little fiddling. No bother at all. Why is it now so difficult?
>
> Paul
>
> "Mike '/m'"  wrote in message
> news:kd22uu8f27rhlglqnsim48smlf1k6jdvhi{at}4ax.com...
> > On Sat, 23 Nov 2002 12:37:35 -0500, "Robert Comer"
> >  wrote:
> >
> > >> Why doesn't it 'just work'?
> > >
> > >Good question.
> >
> >
> > Because Windows networking is a tangle of proprietary protocols,
> > half-baked code, and gawd-awful spaghetti code.   The Samba team is
> > one of the folk trying to get Microsoft to open up their protocols.
> >
> > Bottom line: Micorosft does not want Samba to "just work".
> >
> >  /m
> >
>

--- BBBS/NT v4.01 Flag-4