Displaying 3 results from an estimated 3 matches for "winbinidd".
Did you mean:
winbindd
2023 Jan 30
4
Using separate packages for a DC
...don't share anything. One only have to specify
different IP addresses for the two (and different names),
and that's about it.
I'm not yet sure about all the details, - for example, there can
only be one libnss_winbind, but in this case it looks like the
regular instance don't need winbinidd, single winbind can be used.
There's a question about DNS too. That all needs to be thought
about for *sure*.
If that works, the two might be built with different kerberos
implementations as well: the regular fileserver (and client)
is built with MIT kerberos which is more featureful, and the...
2023 Jan 31
1
Using separate packages for a DC
...specifydifferent IP addresses for the two (and different names),and
> that's about it.
I would really not do that.
> I'm not yet sure about all the details, - for example, there canonly
> be one libnss_winbind, but in this case it looks like theregular
> instance don't need winbinidd, single winbind can be used.There's a
> question about DNS too. That all needs to be thoughtabout for
> *sure*.
> If that works, the two might be built with different
> kerberosimplementations as well: the regular fileserver (and
> client)is built with MIT kerberos which is more...
2023 Jan 30
1
Using separate packages for a DC
...only have to specify
> different IP addresses for the two (and different names),
> and that's about it.
>
> I'm not yet sure about all the details, - for example, there can
> only be one libnss_winbind, but in this case it looks like the
> regular instance don't need winbinidd, single winbind can be used.
> There's a question about DNS too.? That all needs to be thought
> about for *sure*.
>
> If that works, the two might be built with different kerberos
> implementations as well: the regular fileserver (and client)
> is built with MIT kerberos whi...