Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
Fredrik Ohrn wrote: It seems that Samba 2.2.8 is unable to open TDB files written by older versions. Instead it just overwrites them with a fresh file. This caused our domain-server to loose the domain SID leaving all our NT clients out in the cold. We use a domain SID extracted from the previous PDC, an old WinNT 4.0 server that was scrapped. Our print server also lost it's registry of printerdrivers and settings. To verify this yourself, try the tdbtool utility. The 2.2.8 version can't open old TDB files. The other way round works though, tdbtool from 2.2.7a can open new TDB files written by 2.2.8. To salvage the domain SID I copied smbpasswd.c from 2.2.8 into a 2.2.7a source tree and compiled it, then I could use the new -X and -W options to extract the SID from the old secrets.tdb and write it into a fresh TDB from 2.2.8. I'm still working on the printersettings... Anyway, if anyone can replicate this I'd suggest that 2.2.8 should be retracted or atleast a big fat warning should be posted that you may loose your domain SID effectively killing your domain-controller. Hmm, at least secrets.tdb and winbind_idmap.tdb survived the upgrade well on four machines here, previous versions 2.2.7a and 2.2.6. All of them running as domain members, however, none being DC... Cheers! Michael
Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
On Sun, 16 Mar 2003, Fredrik Ohrn wrote: To salvage the domain SID I copied smbpasswd.c from 2.2.8 into a 2.2.7a source tree and compiled it, then I could use the new -X and -W options to extract the SID from the old secrets.tdb and write it into a fresh TDB from 2.2.8. I am glad to be of help :-) Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com
Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
Le dim 16/03/2003 à 19:01, Richard Sharpe a écrit : On Sun, 16 Mar 2003, Fredrik Ohrn wrote: To salvage the domain SID I copied smbpasswd.c from 2.2.8 into a 2.2.7a source tree and compiled it, then I could use the new -X and -W options to extract the SID from the old secrets.tdb and write it into a fresh TDB from 2.2.8. I am glad to be of help :-) Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com Ok, can anyone are sure that the upgrade read old tbd file. I use samba 2.2.7a and OpenLdap, I am not connected to the internet, but the point 51 are very interesting for my problem (submited in samba-list). My server will become in production. I don't would like lose my SID and workstation SID. can I have a answer today ? thanks Stéphane Purnelle
Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
Fredrik Ohrn wrote: It seems that Samba 2.2.8 is unable to open TDB files written by older versions. Instead it just overwrites them with a fresh file. This caused our domain-server to loose the domain SID leaving all our NT clients out in the cold. We use a domain SID extracted from the previous PDC, an old WinNT 4.0 server that was scrapped. Our print server also lost it's registry of printerdrivers and settings. I have not seen any problem on the two Samba PDC's I upgraded (although my test system went from 2.2.7a to 2.2.8 via 2.2.8pre2). I seem to be able to logon as a domain user and access network drives OK. Roaming profiles seem to copy OK. I can use rpcclient to enumerate drivers OK, but I have not really been using Samba for printing because of the printer settings problem on Solaris (hopefully fixed now). I only have Windows 2000 clients. It is probably worth posting more information about your setup. Regards Nick
Re: Showstopper! Samba 2.2.8 can't read TDB files from previousversions.
On Sun, 16 Mar 2003, Nicholas Brealey wrote: Fredrik Ohrn wrote: It seems that Samba 2.2.8 is unable to open TDB files written by older versions. Instead it just overwrites them with a fresh file. This caused our domain-server to loose the domain SID leaving all our NT clients out in the cold. We use a domain SID extracted from the previous PDC, an old WinNT 4.0 server that was scrapped. Our print server also lost it's registry of printerdrivers and settings. I have not seen any problem on the two Samba PDC's I upgraded (although my test system went from 2.2.7a to 2.2.8 via 2.2.8pre2). I seem to be able to logon as a domain user and access network drives OK. Roaming profiles seem to copy OK. I can use rpcclient to enumerate drivers OK, but I have not really been using Samba for printing because of the printer settings problem on Solaris (hopefully fixed now). I only have Windows 2000 clients. It is probably worth posting more information about your setup. Regards Nick We upgraded from 2.2.7a to 2.2.8. Server OS is RedHat 8.0. The sectrets.tdb file was created a log time ago with an older version and some hacking around with tdbtool to insert the SID. After more than a cursory look the print-server did infact keep it's settings. It has lost information about some but not all of the printers but we have had that problem before so it's not related to the upgrade. I can post the old sectrets.tdb file that gets instantly replaced by samba 2.2.8 in case that is of any help. Regards, Fredrik -- Only two things are infinite, the universe and human stupidity; and I'm not sure about the former. - Albert Einstein Fredrik Öhrn Chalmers University of Technology [EMAIL PROTECTED] Sweden
