Hi Ian,
the nt 4 domain schema ( which is valid for samba )
resides in a pdc and bdcs ( this is done via ldap replication with samba
), so if the pdc istn allive the bdc will you give auth for logon with a
windows client.
The problem is ,a users home or/and roam profile can only be hosted on
one place, so if the server ( smb pdc, bdc,nas whatever) which is
hosting the
homes and profiles, is down, there is no chance to get home and/or
profile at logon,cause this is a unique entry in ldap.
So a real backupserver on the fly is not possible with nt4,
in case the pdc is not longer online the bdc must be upgraded to pdc
and/or the home/profile files must be copied with all user permissions
to i.e the new pdc ( i.e. upgraded from bdc, or other online smb/cifs
machines ) and the entries of the users homes/profiles must be changed
to point there.
for shure you can use rsync ( or equals) to have files/profiles/homes
synced with your pdc so you would have them online in case of failures.
I guess this will be better with samba 4 as it acts as ad controller (
but i am not sure),
but for now i see no "cheap" solution which makes which makes it
possible to have backup servers full functionally without any admin
intervention in case of failures.
I maybe fail , but in this case Jerry will have the right stuff
for you , i never used this patch because i see no real sense in it,
having pdc and bdc rightly configured.
Best Regards
Ian Barnes schrieb:> Hi,
>
>
>
> I am using a patch that Jerry wrote that will auto discover any secondary
> servers on your network and if the one its joined to dies, it will join
> another one. That's fine, I can join and everything works fine, until I
> unplug the server im joined to. It takes a few minutes to kill over, and
> once its detected that its dead, it swaps over and I get this if I then try
> wbinfo -a username%pass:
>
>
>
> plaintext password authentication failed
>
> error code was NT_STATUS_NO_TRUST_SAM_ACCOUNT (0xc000018b)
>
> error messsage was: No trusted SAM account
>
> Could not authenticate user Administrator%password with plaintext password
>
> challenge/response password authentication failed
>
> error code was NT_STATUS_NO_TRUST_SAM_ACCOUNT (0xc000018b)
>
> error messsage was: No trusted SAM account
>
> Could not authenticate user Administrator with challenge/response
>
>
>
> Any ideas as to why this happens when it fails over? I can logon to both
> servers individually and everything works fine if they are both up, only if
> one dies, does this happen.
>
>
>
> Thanks
>
> Ian
>
>
>
>
>
--
Mit freundlichen Gruessen
Best Regards
Robert Schetterer
robert_at_schetterer_dot_org
Munich / Bavaria / Germany
https://www.schetterer.org