[Samba] Re-establishing a Samba 2.2.1a domain controller after major "crash"

[Lasse Taul Bjerre]

I've now, stopped samba, removed all the files in /etc/samba/, restored them
from the backup, and started samba again. And It had absolutly no effect.
The "Trust Relationship" between the workstaions and the server is still
gone :(
Guess there is no way out of it, I have to rejoin all the workstations :(

On the upside, samba 2.2.6 seems faster than 2.2.1a - and it compiled
without any problems what so ever :)

Is there a place i can find a list of major differences, and feature
enhancements between 2.2.1a and 2.2.6?

/Lasse

-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]On
Behalf Of Andrew Bartlett
Sent: 26. oktober 2002 01:24
To: Lasse Taul Bjerre
Cc: samba at lists.samba.org
Subject: Re: [Samba] Re-establishing a Samba 2.2.1a domain controller
after major "crash"


Lasse Taul Bjerre wrote:
>
> Our Samba 2.2.1a domain controller suffered a major disk error the other
> day. The partition with /etc and /dev died. :(
> I?ve now reinstalled SuSE 7.3, and re-established the UNIX password files
> (passwd, group, shadow) from backup, further more I?ve re-established the
> files from /etc/samba (MACHINE.SID, groups.mapping, lmhosts, machine.sid,
> secrets.tdb, smb.conf, smbpasswd, smbusers).
>
> All my shares are up and running and the users can log on to the server,
and
> they can map the shares. The only, but major, problem I experiences is:
The
> workstations has lost the ?thrust? to the domain controller. If I check
the
> /etc/samba/smbpasswd file the ?Machine Trust Account? exists. Have I
missed
> a file or something, or is it just not possible to re-establish a domain
> controller via the config files?
>
> ANY help is MUCH appreciated, this is a domain with 250 computers, and so
> going around and rejoining all the computers is to time consuming. And I
> would really like to have the system back online Monday morning.

Ensure that you copy across *all* the mentioned files, and before you
start smbd.  Also, ensure you must use exactly the same hostname.  If
you have the misfortune to start smbd without the old secrets.tdb in
place, or the hostname changed, it will regenerate the SID, causing this
problem.

> Further more, I plan to upgrade to 2.2.6 ASAP (when I've solved the Trust
> issue) Is this a good version or should I use an older version like 2.2.5
> or??

2.2.6 is a 'good' version, as far as we can tell :-).

(The pre and RC releases cleaned out quite a number of nice little
bugs).

Andrew Bartlett

--
Andrew Bartlett                                 abartlet at pcug.org.au
Manager, Authentication Subsystems, Samba Team  abartlet at samba.org
Student Network Administrator, Hawker College   abartlet at hawkerc.net
http://samba.org     http://build.samba.org     http://hawkerc.net
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba