[Samba] Samba Print Problem (Everything Looks Right)

Brian White bcwhite at precidia.com
Tue May 23 00:36:49 GMT 2006

> Try 'guest ok = yes' - otherwise any slight change in credentials will
> block access to the print$ share - and anyway, it shouldn't matter if
> an unauthorised user can copy your driver files ;-)

Tried that, but it didn't make any difference.

>>In fact, when I double-click to open the printer, it does connect and 
>>give me a print-queue window.  It's only when I trying to bring up
>>the properties for that printer that it tells me no driver is
>>installed and asks if I want to search for one.
> This is the classic scenario of 'the driver was never originally
> installed' - I don't know if you can successfully install it from here,
> I've always deleted the locally installed printer and then gone back to
> the server and double-clicked on the printer again.

I've done that dozens of times now.  I've even gone to a fresh Win2K 
install.  They all say the same thing:

"The 'Doyle' printer driver is not installed on this computer.  Some 
printer properties will not be accessible unless you install the printer 
driver.  Do you want to install the driver now?"

Reading this more carefully...  I originally assumed it meant that it 
couldn't find the printer driver for "Doyle" the printer.  But this says 
it can't find the "Doyle" printer driver, which is (somewhat) different. 
  The "cupsaddsmb" program creates the driver with the same name as the 
printer.  Thus, the printer "Doyle" uses the "Doyle" printer driver.

Anyway...  I did a search on C:\ and found "Doyle.BPD" and "Doyle.ppd" 
in C:\WINDOWS\system32\spool\drivers\w32x86\3, so it has found and 
copied all 8 files to that directory (cupsui6.dll, cupsps6.dll, 
cups6.ini, pscript.ntf, pscript.hlp, ps5ui.dll, Doyle.ppd, and 

>>However, even if I say "no", the properties dialog does come up (just 
>>the print queue settings -- no printer driver options) and I can 
>>successfully print a test page.
> Yes, Windows will display the standard pages that aren't driver
> specific.  That's odd that you can print a test page though.
>>So...  What am I missing?
> Did you install the PostScript driver or the CUPS driver?  From your
> last post it looks like both are installed at the same time - but as
> I've never used the CUPS driver, that might be normal.  Although it
> could explain why you were able to print (via one driver) but not
> display the properties (problem with the other driver.)

The cups driver seems to be an extension of the Microsoft one.  You have 
to copy _both_ sets to the /usr/share/cups/drivers directory (something 
far from clear in the man page) before the "cupsaddsmb" script will work.

> When you double-click on the printer on the server (assuming it's not
> installed locally) that's when it tries to copy the driver across.
> What happens when you do this?

It seems to work.  It opens the queue window.  I haven't seen any jobs 
on it, but then I'm just re-building the network here, so there isn't 
anyone else around to print.

If I try to open the "properties" for the printer I'll get the error 
mentioned above.

This whole thing summarizes what I hate most about Windows...  When it 
doesn't work, it's darn near impossible to find out why!  No "strace", 
no source code, no logs, nothing.

                                  ( bcwhite at precidia.com )

           Until we are first independent, we cannot be interdependent.

More information about the samba mailing list