That is what we did not do, thanks a ton Gary! This will certainly save us a ton of headaches in the future. On 9/14/05, Gary MacKay <gary@edisoninfo.com> wrote:> > linux starved wrote: > > On 9/13/05, Paul Gienger <pgienger@ae-solutions.com> wrote: > > > >>>We recently suffered a server loss, during the power an unforgiving > >> > >>power > >> > >>>outage. I built a new machine, copied over all information contained in > >>>the > >>>home directory, and also copied shadow, shadow passwd, groups, passwd. > >> > >>Did you even bother with any of the samba information? The smbpasswd, > and > >>tdb files? > > > > > > > > We copied the enitre samba directory over, renaming all default install > > files i.e.smbpasswd to smbpasswd_default > > > But did you get the /var/lib/samba and/or /var/cache/samba files? They > contain all of the SID info and such. > > > > >>I was able to set the permissions and ownership they way it was on the > old > >> > >>>server, and everything looked well. However when I asked the users to > >> > >>log > >> > >>>in, they couldn't. Is there a file I should have copied over, that > would > >>>"trick" these machines into thinking they were authenticating to the > old > >>>samba server? > >> > >>More info please!!!What errors > > > > > > > > I cannot give an exact message error since it is a remote office but it > is > > close to, > > > > 'The system cannot log you on to this domain because the system's > computer > > name is missing or the password on the account is incorrect.' > > > > > >>We are running debian sarge on the 2.6.8 kernel and samba version > 3.0.14a- > >> > >>>3. > >>>All help is appreciated, thank you in advance. > >>>-- > >>>To unsubscribe from this list go to the following URL and read the > >>>instructions: https://lists.samba.org/mailman/listinfo/samba > >> > >> > >