Samba 2.2.8a-1, RH8.
... So, I had to reinstall. Fortunately I had a back-up copy. I've installed
everything and then went to back-up and brought back all the stuff from
/etc/samba and /var/cache/samba and all /etc/cups and /etc/printcap*.
Aparently samba is working corectly: All user/machine accounts are in place
winbind OK... It's just that although I've restored the /home/printers
folder in the previous state it looks like I've lost my printer drivers.
Rpcclient enumdrivers shows empty hands although the driver files are in the
corresponding folder! Printing directly to CUPS works without any problem
and using the same config files it worked before the "move".
Logs for the machine trying to print looks like:
[2003/07/01 15:41:08, 0] printing/pcap.c:pcap_printername_ok(289)
Unable to open printcap file cups for read!
[2003/07/01 15:41:08, 0] smbd/service.c:make_connection(252)
ws130 (191.x.y.130) couldn't find service
::{2227a280-3aea-1069-a2de-08002b30309d}
[2003/07/01 15:42:00, 1] smbd/service.c:make_connection(636)
Of course printcap is there in /etc and it is 644. Did I forgot to copy
something? Anybody with a hint?
Vizitiu, Ciprian CVizitiu at gbif.org> Tue Jul 1 16:58:12 GMT 2003 > > Samba 2.2.8a-1, RH8. > > ... So, I had to reinstall. Fortunately I had a back-up copy. I've installed > everything and then went to back-up and brought back all the stuff from > /etc/samba and /var/cache/samba and all /etc/cups and /etc/printcap*. > Aparently samba is working corectly: All user/machine accounts are in place > winbind OK... It's just that although I've restored the /home/printers > folder in the previous state it looks like I've lost my printer drivers. > Rpcclient enumdrivers shows empty hands although the driver files are in the > corresponding folder! Printing directly to CUPS works without any problem > and using the same config files it worked before the "move". > > Logs for the machine trying to print looks like: > > [2003/07/01 15:41:08, 0] printing/pcap.c:pcap_printername_ok(289) > Unable to open printcap file cups for read! > [2003/07/01 15:41:08, 0] smbd/service.c:make_connection(252) > ws130 (191.x.y.130) couldn't find service > ::{2227a280-3aea-1069-a2de-08002b30309d} > [2003/07/01 15:42:00, 1] smbd/service.c:make_connection(636) > > Of course printcap is there in /etc and it is 644. Did I forgot to copy > something?Yes, the "Registry"....> Anybody with a hint?Samba stores printer driver information (including DeviceMode etc.) in its own equivalent to the Windows Registry, the "*.tdb" files. These should also be restored to get everything up and running as before.... Cheers, Kurt
> > > > Of course printcap is there in /etc and it is 644. Did I forgot to > > copy something? > > Yes, the "Registry".... > > > Anybody with a hint? > > Samba stores printer driver information (including DeviceMode > etc.) in its own equivalent to the Windows Registry, the > "*.tdb" files. These should also be restored to get > everything up and running as before....Hmmm... I've restored ALL the content of /etc/samba and /var/cache/samba. Please tell me that there are other places where samba keeps tdbs... Because otherwise I've restored them all. :-/ Is the printers "registry" different than the users one? Because the rest of the samba seems to be working domain auth and like.
Vizitiu, Ciprian CVizitiu at gbif.org> Tue Jul 1 17:50:13 GMT 2003 >....>> > Of course printcap is there in /etc and it is 644. Did I forgot to >> > copy something? >> >> Yes, the "Registry".... >> >> > Anybody with a hint? >> >> Samba stores printer driver information (including DeviceMode >> etc.) in its own equivalent to the Windows Registry, the >> "*.tdb" files. These should also be restored to get >> everything up and running as before.... > > Hmmm... I've restored ALL the content of /etc/samba and /var/cache/samba. > Please tell me that there are other places where samba keeps tdbs...This differs from distribution to distribution. It is a compile-time option. IIRC, on my other box some of the tdbs were in /usr/lib/samba/> Because > otherwise I've restored them all. :-/ Is the printers "registry" different > than the users one?I don't understand what you mean with "users registry". The *.tdb files relevant for printing are printing.tdb, nt_forms.tdb, ntprinters.tdb, ntdrivers.tdb. The the *.tdb stuff has changed slightly from 2.2.x to 3.0. I guess you are running 2.2.x ? The only thing I can say is that I have successfully restored the whole printing setup covering dozens of printers already twice (some time ago) by restoring the *.tdbs plus the other Samba files.> Because the rest of the samba seems to be working domain > auth and like.