Account Database replication

[MCCALL,DON (HP-USA,ex1)]

Hi John,
Afraid you have run into one of the failings of samba at this point -
redundancy.  BDC capability is planned for a future release, but it's not
here now.
DEPENDING on how you are handling user authentication on your samba pdc, you
could possibly use scripts to copy your smbpasswd file from the pdc to the
other samba servers, so that when they fail to contact the pdc, they will
fallback to checking the smbpasswd file to see if they can resolve the
name/passwd pair locally.  But this would require that you also have your
/etc/passwd files in sync as well, or all of your unix servers using nis for
username lookups from the same NIS server.
This would at least allow your users to locally authenticate on the samba
server that contains the share they are trying to access, when the PDC is
unavailable....
Better heads than mine probably have more ideas on working around this...

Sorry,
Don

-----Original Message-----
From: John Humphrey [mailto:txkjohn at hotmail.com]
Sent: Monday, April 16, 2001 2:26 PM
To: samba-ntdom at lists.samba.org
Subject: Account Database replication


First of all... I'm very greatful for all the applicable info posted to this

mailing list.

Now to my quesiton. We've just begun to implement samba in our network. We 
have multiple locations connected via frame relay. I want to run only one 
'domain'. I've configured my samba 2.0.7 as a PDC and it works great. I have

one problem... Our frame relay circuits go down about once a month... If the

other samba servers cannot communicate with the samba PDC, how will the 
users on the 'wrong' side of the broken link authenticate?  In other words, 
can samba 2.0.7 be a BDC? If not, is there any other way to 'trick' samba 
into replicating its user account database with each of the remote samba 
servers?




_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com