Re: [Samba] ldap machine suffix fixed?

Jim C. wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Is there any problem to be fix on samba side? I've been using separate container for machine without any problem ( almost 8 months

Re: [Samba] ldap machine suffix fixed?

Beast wrote: Jim C. wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Is there any problem to be fix on samba side? I've been using separate container for machine without any problem (

Re: [Samba] ldap machine suffix fixed?

Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Is there any problem to be fix on samba side? I've been using separate container for machine without any problem ( almost 8 months now) Same, always have, never had this problem. -- To

Re: [Samba] ldap machine suffix fixed?

Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Is there any problem to be fix on samba side? I've been using separate container for machine without any problem ( almost 8 months now) Yes, there was a problem, and maybe still is.

Re: [Samba] ldap machine suffix fixed?

Tomasz Chmielewski wrote: Beast wrote: Jim C. wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Is there any problem to be fix on samba side? I've been using separate container for machine

[Samba] ldap machine suffix fixed?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Did ldap machine suffix ever get fixed so that it can be in a sperate container from ldap user suffix? Jim C. - -- - - | I can be reached on the following Instant Messenger services: |