I would like to be able to change between backends but I'm worried that
my users will encounter trouble loggin in. So I'm looking for
reassurance that my command is ok.
My current configuration is:
passdb backend = ldapsam:ldap://10.10.10.10 smbpasswd guest
I would like to change from ldap t
An inherited system has the following configuration:
passdb backend = ldapsam:ldap://10.10.10.10 smbpasswd guest
What is the purpose of using multiple backends? The smb.conf man page
simply states that each backend will be searched in turn but why would
one ever use such a setup?
Secondly, t
--- Gary Dale <[EMAIL PROTECTED]> wrote:
> Peter Matulis wrote:
> > I have a new PDC ready to replace an older one (which is using LDAP
> > locally). The new one will be using tdbsam.
> >
> > I plan to first change LDAP on the existing system to the tdb
I have a new PDC ready to replace an older one (which is using LDAP
locally). The new one will be using tdbsam.
I plan to first change LDAP on the existing system to the tdbsam
backend and ensure proper functioning. I understand I can use the
pdbedit tool to make this change. Comments?
At this
eing managed.
What is the separate step you mention? Can I export the data out of
LDAP?
Thanks for your help.
> Peter Matulis wrote:
> > I have inherited a Samba server and would like to migrate the
> > installation to a new machine. We are using Samba as a PDC and my
> &g
I have inherited a Samba server and would like to migrate the
installation to a new machine. We are using Samba as a PDC and my
currrent worry is what users will see on their desktop (as well as
other changes?) once they log on to the new server.
As a test I have logged on with my laptop (running
