samba - Mar 2003 - Difficulty with Samba 2.2.8 and native CUPS PS drivers

I've recently attempted to convert from the Adobe PostScript drivers for my 
Canon BJC=2110 printer over to the native CUPS Windows PS drivers and can't 
quite get things to work correctly.  After deleting the printer on my 
WinXP SP1 clients, verifying under "Server Properties" that the Adobe
driver
was removed, then reconnecting to my Samba printer, I connect fine but receive 
the error that the "printer drive is not installed on this computer"
when
attempting to go into properties or print to that device.

Checking out the C:\WINDOWS\System32\spool\DRIVERS\W32X86\2 directory shows 
the following files:
	Canon_BJC.ppd
	cups.hlp
	cupsdrvr.dll
	cupsui.dll

Going into the registy, at HKLM\System\ControlSet001\Control\Print\
Environments\Windows NT x85\Drivers\Version-2\Canon_BJC I do have entries 
to the various CUPS driver files.  I'm not familiar with what all the values
at this location should be set, but I don't see anything obviously broken.

Printing directly from the CUPS server via lp commands works fine.  

I'd appreciate any pointers to corect this problem.  Thanks!  

Below is my smbd.conf file for reference:


[global]
log level = 1 
oplocks = yes
level2 oplocks = yes

workgroup = DEADHEAVEN

server string = Geoff - The Deadheaven Domain Server
hosts allow = 192.168.0.

printer admin = davidski cnilan
load printers = yes
printcap name = cups
printing = cups
log file = /var/log/log.%m
max log size = 500

security = user
encrypt passwords = yes
lanman auth = no
socket options = TCP_NODELAY 
interfaces = 192.168.0.1/24

domain master = yes 
domain admin group = root davidski
preferred master = yes
domain logons = yes

logon script = startup.bat
logon path = \\%N\profiles\%U
wins support = yes

dns proxy = no 

[homes]
    comment = Home Directories
    browseable = no
    writeable = yes

[netlogon]
    comment = Network Logon Service
    path = /usr/local/samba/lib/netlogon
    guest ok = yes
    writeable = no
    ;share modes = no


[profiles]
    path = /usr/local/samba/profiles
    browseable = no
    writeable = yes
    guest ok = no
    create mask = 0700
    directory mask = 0700
    nt acl support = no
    share modes = no
    csc policy = disable

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
use client driver = no
public = yes
guest ok = yes
writeable = no
printable = yes
printer admin = davidski

[tmp]
   comment = Temporary file space
   path = /usr/local/samba/tmp
   read only = no
   writeable = yes
   public = yes
   browsable = yes

[mp3]
   comment = MP3 Share
   path = /usr/home/davidski/mp3
   public = yes
   writeable = yes
   printable = no
   write list = davidski

[print$]
comment = Printer Drivers
path = /usr/local/samba/printers
guest ok = no
browseable = yes
read only = yes
write list = root davidski

David F. Severski davidski-samba at deadheaven.com wrote on Samba-Digest:
> Sat Mar 29 10:11:19 GMT 2003
> 
> I've recently attempted to convert from the Adobe PostScript drivers
for my
> Canon BJC=2110 printer over to the native CUPS Windows PS drivers
You can only do this if your CUPS version is sufficiently new.
Check by reading "man cupsaddsma". Does it already relate to the
CUPS PostScript drivers?
> and can't 
> quite get things to work correctly.  After deleting the printer on my 
> WinXP SP1 clients, verifying under "Server Properties" that the
Adobe driver
> was removed, then reconnecting to my Samba printer, I connect fine but
receive
> the error that the "printer drive is not installed on this
computer" when
> attempting to go into properties or print to that device.
Which version of Samba and CUPS are you using?

You might need to restart Samba to get it to work (if you have the printer
"Canon_BJC", or any other, newly installed).

If this doesn't help, let root do a

    "smbcontrol smbd debug 3"

and then watch

    "tail -f /var/log/samba/log.smbd"    (or appropriate path)

while you try to connect to Samba from XP.

Make sure the connection is as a user who can write to the [print$] share.
Check which user you are from Samba's point of view, by asking for

    "smbstatus"

If you had unfortunately been connected as "nobody" (or another user
with
a less priviledge account), kill all connections. But that is not enough:
you need to also close all Explorer windows on the client and connect *as
first thing* via a "DOS window":

   "net use \\sambaserver\print$ /user:root"

(instead of root, you could use a username priviledged enough to write to
the print$ share).

The problem is a bug on MS Win: they seem to cache info they received
previously from Samba (or a Win NT printer server) for as long as the
Explorer is open, and keep repeating the same message about "unavailable
driver files" without even asking again the Samba server for an update...
> 
> Checking out the C:\WINDOWS\System32\spool\DRIVERS\W32X86\2 directory shows
> the following files:
> 	Canon_BJC.ppd
> 	cups.hlp
> 	cupsdrvr.dll
> 	cupsui.dll
> 
> Going into the registy, at HKLM\System\ControlSet001\Control\Print\
> Environments\Windows NT x85\Drivers\Version-2\Canon_BJC I do have entries 
> to the various CUPS driver files.  I'm not familiar with what all the
values
> at this location should be set, but I don't see anything obviously
broken.
> 
> Printing directly from the CUPS server via lp commands works fine.  
> 
> I'd appreciate any pointers to corect this problem.  Thanks!  
> 
> Below is my smbd.conf file for reference:
> 
> 
> [global]
> log level = 1 
> oplocks = yes
> level2 oplocks = yes
> 
> workgroup = DEADHEAVEN
> 
> server string = Geoff - The Deadheaven Domain Server
> hosts allow = 192.168.0.
> 
> printer admin = davidski cnilan
> load printers = yes
> printcap name = cups
> printing = cups
> log file = /var/log/log.%m
> max log size = 500
> 
> security = user
> encrypt passwords = yes
> lanman auth = no
> socket options = TCP_NODELAY 
> interfaces = 192.168.0.1/24
> 
> domain master = yes 
> domain admin group = root davidski
> preferred master = yes
> domain logons = yes
> 
> logon script = startup.bat
> logon path = \\%N\profiles\%U
> wins support = yes
> 
> dns proxy = no 
> 
> [homes]
>     comment = Home Directories
>     browseable = no
>     writeable = yes
> 
> [netlogon]
>     comment = Network Logon Service
>     path = /usr/local/samba/lib/netlogon
>     guest ok = yes
>     writeable = no
>     ;share modes = no
> 
> 
> [profiles]
>     path = /usr/local/samba/profiles
>     browseable = no
>     writeable = yes
>     guest ok = no
>     create mask = 0700
>     directory mask = 0700
>     nt acl support = no
>     share modes = no
>     csc policy = disable
> 
> [printers]
> comment = All Printers
> path = /var/spool/samba
> browseable = no
> use client driver = no
> public = yes
> guest ok = yes
> writeable = no
> printable = yes
> printer admin = davidski
> 
> [tmp]
>    comment = Temporary file space
>    path = /usr/local/samba/tmp
>    read only = no
>    writeable = yes
>    public = yes
>    browsable = yes
> 
> [mp3]
>    comment = MP3 Share
>    path = /usr/home/davidski/mp3
>    public = yes
>    writeable = yes
>    printable = no
>    write list = davidski
> 
> [print$]
> comment = Printer Drivers
> path = /usr/local/samba/printers
> guest ok = no
> browseable = yes
> read only = yes
> write list = root davidski

David F. Severski davidski at deadheaven.com wrote on Samba-Digest:
> Sun Mar 30 06:55:36 GMT 2003
> 
> 
> Kurt,
> 
> First of all, thank you very much for your time and assistance here.  I
greatly
> appreciate the effort.  Below are my results and some further information.
> 
> On Sun, Mar 30, 2003 at 12:14:01AM +0100, Kurt Pfeifle wrote:
> 
>> >I've recently attempted to convert from the Adobe PostScript
drivers for
>> >my Canon BJC=2110 printer over to the native CUPS Windows PS
drivers
>> 
>> You can only do this if your CUPS version is sufficiently new.
>> Check by reading "man cupsaddsma". Does it already relate to
the
>> CUPS PostScript drivers?
> 
> The cupsaddsmb man page does mention the native CUPS drivers.  Sorry, I
should
> have specified the CUPS version previously.  This is CUPS 1.1.18 running on
> a FreeBSD 4.8-RC (STABLE) machine.  Samba is, again, 2.2.8 and is compiled
with
> the Recycle and SSL options.  Samba, CUPS, and the supporting gimp-print 
> systems were all compiled from source via the FreeBSD ports system.
> 
>> You might need to restart Samba to get it to work (if you have the
printer
>> "Canon_BJC", or any other, newly installed).
> 
> I've done a full stop of Samba, verifying that all smbd and nmbd
processes have
> shut down, then restarted Samba.
> 
>> 
>> If this doesn't help, let root do a
>> 
>>    "smbcontrol smbd debug 3"
>> 
>> and then watch
>> 
>>    "tail -f /var/log/samba/log.smbd"    (or appropriate path)
>> 
>> while you try to connect to Samba from XP.
> 
> No luck there, I'm afraid.  In tests with two machines, both generated
the
> error message about missing driver files, even though the properties of the
> connection show that a Windows NT/2000 driver is installed, and the CUPS 
> native PS driver files are copied successfully into the
Windows\System32\Spool\
> Drivers tree.  Attached are two gzipped log files, smb-desktop.log and 
> smb-laptop.log.  
> 
> smb-desktop.log is an XP SP1 machine that is 
> joined to the domain and logged in with an account that has write 
> privileges to the print$ share.  The desktop had just been rebooted, logged
> in, the existing printer deleted, and the driver removed from the system 
> via the Server Properties function.  No other printers or drivers were 
> installed.
> 
> smb-laptop.log is an XP SP1 laptop that is not part of the domain.  From a 
> command prompt, I connected to the print$ share as root before deleting the
> existing printer connection, removing the printer driver via Server 
> Properties, then reconnected to the printer.
>> 
>> Make sure the connection is as a user who can write to the [print$]
share.
>> Check which user you are from Samba's point of view, by asking for
>> 
>>    "smbstatus"
> 
> Verified to be either root (for the laptop), or my privileged login account
> for the desktop.

David,

can you please verify, that "cupsaddsmb -v [printername]" completes
successfully This means, you need to have the "smbclient" command
putting the files successfully to the "print$" share, and afterwards
read "success" meassages in the output: 2 for the "rpcclient
addriver"
commands and 1 for the "rpcclient setdriver" command...

Cheers,
Kurt

David F. Severski davidski-samba at deadheaven.com wrote on Samba-Digest;
> Mon Mar 31 05:18:11 GMT 2003
> 
> 
> On Mon, Mar 31, 2003 at 12:36:08PM +0200, Kurt Pfeifle wrote:
>> can you please verify, that "cupsaddsmb -v [printername]"
completes
>> successfully This means, you need to have the "smbclient"
command
>> putting the files successfully to the "print$" share, and
afterwards
>> read "success" meassages in the output: 2 for the
"rpcclient addriver"
>> commands and 1 for the "rpcclient setdriver" command...
> 
> Kurt,
> 
> The cupsaddsmb command completes with no errors.  I have also previously 
> deleted the ntdrivers.tdb, ntprinters.tdb, and ntprinters.tdb files, stoped
> and restarted samba, and repeated the cupssmbadd command with no change 
> in results.
How baaaaad -- you're seriously limiting my further options to troubleshoot
this problem.

No, seriously now: I would have suggested to delete the various printing
related *.tdb files next and start all over.
> Below is the output of cupsaddsmb, editted only to obscure the 
> password used, along with a listing of the CUPS drivers in the print$ 
> share:
> 
> File list
> ---------
> root at geoff:/usr/local/samba# ll -R printers/
> total 3
> drwxrwxr-x  3 root  wheel  512 Mar 30 06:29 ./
> drwx--x--x  6 root  wheel  512 Jan 12 11:24 ../
> drwxrwxr-x  3 root  wheel  512 Mar 31 05:10 W32X86/
> 
> printers/W32X86:
> total 3
> drwxrwxr-x  3 root  wheel  512 Mar 31 05:10 ./
> drwxrwxr-x  3 root  wheel  512 Mar 30 06:29 ../
> drwxrwxr-x  2 root  wheel  512 Mar 31 05:10 2/
> 
> printers/W32X86/2:
> total 648
> drwxrwxr-x  2 root  wheel     512 Mar 31 05:10 ./
> drwxrwxr-x  3 root  wheel     512 Mar 31 05:10 ../
> -rwxr--r--  1 root  wheel  120593 Mar 31 05:10 Canon_BJC.ppd*
> -rwxr--r--  1 root  wheel   14234 Mar 31 05:10 cups.hlp*
> -rwxr--r--  1 root  wheel  278380 Mar 31 05:10 cupsdrvr.dll*
> -rwxr--r--  1 root  wheel  215848 Mar 31 05:10 cupsui.dll*
> ---------
> 
> cupsaddsmb -v -a
> ----------------
> Running command: smbclient //localhost/print\$ -N -U'root%12345' -c
'mkdir W32X86;put /var/spool/cups/tmp/3e883e5be9b91 W32X86/Canon_BJC.ppd;put
/usr/local/share/cups/drivers/cupsdrvr.dll W32X86/cupsdrvr.dll;put
/usr/local/share/cups/drivers/cupsui.dll W32X86/cupsui.dll;put
/usr/local/share/cups/drivers/cups.hlp W32X86/cups.hlp'
> added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0
> Domain=[DEADHEAVEN] OS=[Unix] Server=[Samba 2.2.8]
> NT_STATUS_OBJECT_NAME_COLLISION making remote directory \W32X86
> putting file /var/spool/cups/tmp/3e883e5be9b91 as \W32X86/Canon_BJC.ppd
(5353.0 kb/s) (average 5353.0 kb/s)
> putting file /usr/local/share/cups/drivers/cupsdrvr.dll as
\W32X86/cupsdrvr.dll (4530.9 kb/s) (average 4751.5 kb/s)
> putting file /usr/local/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
(3399.8 kb/s) (average 4169.5 kb/s)
> putting file /usr/local/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
(397.2 kb/s) (average 3431.9 kb/s)
> 
> Running command: rpcclient localhost -N -U'root%12345' -c
'adddriver "Windows NT x86"
"Canon_BJC:cupsdrvr.dll:Canon_BJC.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"'
> cmd = adddriver "Windows NT x86"
"Canon_BJC:cupsdrvr.dll:Canon_BJC.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
> Printer Driver Canon_BJC successfully installed.
> 
> Running command: rpcclient localhost -N -U'root%12345' -c
'setdriver Canon_BJC Canon_BJC'
> cmd = setdriver Canon_BJC Canon_BJC
> Succesfully set Canon_BJC to driver Canon_BJC.
> ----------------
> 
> Again, thanks for your help!
> 
> David
OK then -- lets troubleshoot a bit more...

First off: I have not yet tested 2.2.8 myself, so the following hints are
only a guideline of what I'd do to find out what's going on and what
feils.

I don't remember if you posted your smb.conf already. Please do in your
next posting, should the problem persist (but strip the comments and empty
lines:

    grep -v "^#" /etc/samba/smb.conf | grep -v "^$" | grep
-v "^;"

( Never mind -- I've found it now. But I leave this in for the benefit of
other
readers -- it may avoid some traffic in the future... ;-)   But I can't see
a mention of your OS, and the source of your CUPS and Samba installations.
Self-compiled? Vendor-provided packages? )

And your "smbd" is linked against "libcups"? Check for

    "ldd `which smbd`| grep libcups"


1st step:
--------
Make sure you've a decent level of debuglevel enabled. Start with
"3" (to
not get drowned in too much of output), and increase later should you need
it. Root can change the debuglevel "on the fly" with this command:

   "smbcontrol smbd debug 3"

Root can also check the current debuglevel:

   "smbcontrol smbd debuglevel"


2nd step:
---------
Open an xterm and watch the messages being written to the Samba smbd log
file as you proceed:

    "tail -f /var/log/samba/log.smbd"



3rd step:
---------
Check if Samba sees the printer and the driver:

    "rpcclient -U root%1234 localhost -c "enumprinters"
    "rpcclient -U root%1234 localhost -c "enumdrivers"

where "1234" is the password for root to access Samba (use
"smbpasswd" to set
it up. Note, that "enumprinters" and "enumdrivers" may be
made more verbose
by giving a level paramenter. "enumprinters" takes "0",
"1" and "2".
"enumdrivers" takes "1", "2" and "3".
Both default to "1". Please test if you
can get the highest level for "enumdrivers":

     "rpcclient -U root%1234 localhost -c "enumdrivers 3"

It should display the full paths of the driver files in "UNC
notation", like
this example:

Printer Driver Info 3:
         Version: [2]
         Driver Name: [mopi]
         Architecture: [Windows NT x86]
         Driver Path: [\\10.160.50.23\print$\W32X86\2\cupsdrvr.dll]
         Datafile: [\\10.160.50.23\print$\W32X86\2\mopi.PPD]
         Configfile: [\\10.160.50.23\print$\W32X86\2\cupsui.dll]
         Helpfile: [\\10.160.50.23\print$\W32X86\2\cups.hlp]

         Dependentfiles: []
         Dependentfiles: [v]
         Dependentfiles: [X]

         Monitorname: []
         Defaultdatatype: [RAW]


4th step:
---------
If the second step fails to complete successfully, a real Windows
NT/2K/XP client will also have difficulties to download the drivers.
(OTOH, a failure here could also be due to a bug in Samba's rpcclient
implementation...  ;-)


5th step:
---------
 From your Win OS client, open the "Network Neighbourhood", browse to
the Samba server, open the "Printers" folder there, right-click on
your
printer and select "Connect..." (or "Install..." or whatever
it reads
in an English version of your Win OS).


Other ideas:
------------
* Verify that it still works with the Adobe printer driver files....
* Verify that you have the same CUPS driver files as I do


Kurt [ will try to install Samba 2.2.8 tonight so we talk from the
        same basis...]


P.S.: Sorry -- I re-read your first postiong, and I think I missed
       something there. You write that you *do* have the driver files
       on the WinXP in the
"C:\WINDOWS\System32\spool\DRIVERS\W32X86\2\"
       directory. By which procedure did you bring this about?

       Furtheron, you say you had "the Adobe driver was removed, then
       reconnecting to my Samba printer, I connect fine but "... -- How
       did you bring this "reconnection" about?

       My suggested procedure above (5th step) will do both things at
       once:
          -- transfer and setup the driver files, and
          -- create the printer and the print path.

       Please try this now: delete the printer in your WinXP client's
       local "Printers" folder, browse to the Samba server's
"Printers"
       folder via "Network Neighbourhood" and install the printer by
       right-clicking and selectiong "Connect..."

       I've never seen this failing in such a way that you have the
       driver files transferred successfully to the "...\W32X86\2\"
       directory, but can't print... The sort of failures I've seen are

         --a  "cupsaddsmb" not completing successfully, or/and
         --b  the method I described for downloading/installing driver/printer
              failing with an error message.

       I've not seen someone attempting to "reconnect" a printer
that had
       the Adobe driver files installed previously....

Kurt Pfeifle wrote:
> Other ideas:
> ------------
> * Verify that it still works with the Adobe printer driver files....
> * Verify that you have the same CUPS driver files as I do
Sorry, forgut to paste the info in:

kde4@kde-bitshop:~> ls -tlar /usr/share/cups/drivers/

-r--r--r--  1 root  root   14234 Sep 24  2002 cups.hlp
-r--r--r--  1 root  root  215848 Oct  1 22:49 cupsui.dll
-r--r--r--  1 root  root  278380 Oct  1 22:49 cupsdrvr.dll

Cheers,
Kurt

David F. Severski davidski-samba at deadheaven.com wrote:
> Tue Apr 1 05:27:58 GMT 2003
> 
> 
> Kurt,
> 
> Thanks for the detailed checklist.  It, and your help, are very much 
> appreciated.
> 
> On Mon, Mar 31, 2003 at 07:49:58PM +0200, Kurt Pfeifle wrote:
>> readers -- it may avoid some traffic in the future... ;-)   But I
can't see
>> a mention of your OS, and the source of your CUPS and Samba
installations.
>> Self-compiled? Vendor-provided packages? )
> 
> The OS is FreeBSD 4.8-RC (STABLE) with CUPS, Samba, and all supporting 
> print packages (gimp-print, etc.) compiled from source via the FreeBSD
ports
> system.  Samba was compiled with the recycle and SSL options, though
neither
> of those functions are currently used in my setup.
> 
>> And your "smbd" is linked against "libcups"? Check
for
>> 
>>    "ldd `which smbd`| grep libcups"
> 
> Cups is linked, as show below:
> 
> davidski at geoff:~$ ldd `which smbd`
> /usr/local/sbin/smbd:
>         libssl.so.3 => /usr/lib/libssl.so.3 (0x281bc000)
>         libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x281eb000)
>         libcups.so.2 => /usr/local/lib/libcups.so.2 (0x282e2000)
>         libpam.so.1 => /usr/lib/libpam.so.1 (0x282fb000)
>         libpopt.so.0 => /usr/local/lib/libpopt.so.0 (0x28305000)
>         libc.so.4 => /usr/lib/libc.so.4 (0x2830c000)
> 
> I've just completed a round of tests, with the full procedure and
results
> listed below.  Since it's rather lengthy, I'll summarize here: 
Using the
> CUPS PS driver, I cannot rectify the error where Windows claims the driver
is
> not installed.  Also, enumprinters 3 causes a core dump in rpcclient,
though
> levels 2 and below complete.
> 
> Removing the CUPS drivers from both Samba and the Windows client, then 
> reinstalling the Adobe driver, allows Windows clients to connect, and print
> properly.
> 
> The procedure and results are as follows:
[ ...have not been able to carefully study your session protocol -- will do
   tomorrow...]

I am nearly on my wits end. Everything further from here will likely involve
increasing the Samba debuglevel to 3 and more and do a detailled analysis of
what is going on and why the WinXP-SP1 client thinks it gets no proper PS
driver files offered....

One quick (new) thought, though:

What is the PPD you use for the Canon_BJC like? Can you post the output of
"head -n 40 /etc/cups/ppd/Canon_PJC.ppd" (or some more or less lines,
to show
the PPD header)?

Can you check the syntax of the PPD online at http://www.cups.org/testppd.php?

Maybe you should also post the problem on one of the CUPS mailing lists, to
draw the CUPS developers' attention to it.

Cheers,
Kurt

David F. Severski davidski-samba at deadheaven.com
> Tue Apr 1 15:53:11 GMT 2003
> 
> 
> On Wed, Apr 02, 2003 at 01:21:41AM +0200, Kurt Pfeifle wrote:
>> One quick (new) thought, though:
>> 
>> What is the PPD you use for the Canon_BJC like? Can you post the output
of
>> "head -n 40 /etc/cups/ppd/Canon_PJC.ppd" (or some more or
less lines, to
>> show
>> the PPD header)?
> 
> Here are the first 40 lines of that file:
> 
> *PPD-Adobe: "4.3"
> *%
> *% For information on using this, and to obtain the required backend
> *% script, consult http://www.linuxprinting.org/ppd-doc.html
> *%
> *% PPD-O-MATIC generated this PPD file. It is for use with all programs 
> *% and environments which use PPD files for dealing with printer capabilty
> *% information. The printer must be configured with a Foomatic backend
> *% filter script. This file and the backend filter script work together to
> *% support PPD-controlled printer driver option access with arbitrary free 
> *% software printer drivers and printing spoolers.
> *%
> *% You may save this file as 'Canon-BJC-2110-gimp-print-ijs.ppd'
> *%
> *%
> *FormatVersion:	"4.3"
> *FileVersion:	"1.1"
> *LanguageVersion: English 
> *LanguageEncoding: ISOLatin1
> *PCFileName:	"GIMP-PRI.PPD"
> *Manufacturer:	"Canon"
> *Product:	"(BJC-2110)"
> *cupsVersion:	1.0
> *cupsManualCopies: True
> *cupsModelNumber:  2
> *cupsFilter:	"application/vnd.cups-postscript 0 cupsomatic"
> *ModelName:     "Canon BJC-2110, Foomatic + gimp-print-ijs"
> *ShortNickName: "Canon BJC-2110, gimp-print-ijs"
> *NickName:      "Canon BJC-2110, Foomatic + gimp-print-ijs"
These "commas" in the *Name fields may be a problem....

Also, Gimp-Print-PPDs tend to be quite large. What is the file
size of this PPD? Could the issue be some limitation regarding
the PPD size to be tranferred from Samba to XP?

Last, this seems to be an "old" style PPD. (I can tell from the
"cupsomatic" filter).

Could you try to generate a new style PPD, starting to surf
Linuxprinting.org from

   http://www.linuxprinting.org/foomatic2.9/

and generating the PPD via

   http://www.linuxprinting.org/foomatic2.9/printer_list.cgi

The new PPDs are fully compliant to the Adobe spec. But they
require you to use the new "foomatic-rip" filter instead of
"cupsomatic". Get foomatic-rip from

  
http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0

OTOH, the same PPD seems to have worked with the Adobe driver
files? Hmm.....

Also, just for the Samba-->XP driver download testing, could
you install a driver with another (simple) PPD, like this:

   "lpadmin -p Canon2 -v parallel://dev/lp0 -E -m laserjet.ppd"

   "cupsaddsmb -v Canon2"

and see if you can install the Canon2 onto XP? It would possibly
limit the scope of possible errors to the PPD in question (or
exclude it)?
> *PSVersion:	"(3010.000) 550"
> *PSVersion:	"(3010.000) 651"
> *PSVersion:	"(3010.000) 652"
> *PSVersion:	"(3010.000) 653"
> *PSVersion:	"(3010.000) 704"
> *PSVersion:	"(3010.000) 705"
> *PSVersion:	"(3010.000) 800"
> *LanguageLevel:	"3"
> *ColorDevice:	True
> *DefaultColorSpace: RGB
> *FileSystem:	False
> 
> Running my local cupstestppd command seems to validate okay, with the
following
> output:
> 
> davidski at geoff:~$ cupstestppd /usr/local/etc/cups/ppd/Canon_BJC.ppd
> FILE: /usr/local/etc/cups/ppd/Canon_BJC.ppd
> 
>     CONFORMANCE TESTS:
>         PASS    DefaultContrast
>         PASS    DefaultCyan
>         PASS    DefaultDensity
>         PASS    DefaultDither
>         PASS    DefaultGSResolution
>         PASS    DefaultImageType
>         PASS    DefaultMagenta
>         PASS    DefaultOutputType
>         PASS    DefaultQuality
>         PASS    DefaultstpBrightness
>         PASS    DefaultstpGamma
>         PASS    DefaultstpSaturation
>         PASS    DefaultYellow
>         PASS    DefaultInputSlot
>         PASS    DefaultMediaType
>         PASS    DefaultPageSize
>         PASS    DefaultPageRegion
>         PASS    Fonts
>         PASS    LanguageEncoding
>         PASS    LanguageVersion
>         PASS    Manufacturer
>         PASS    ModelName
>         PASS    NickName
>         PASS    PageSize
>         PASS    PageRegion
>         PASS    Product
>         PASS    ShortNickName
> 
> Interestingly, the testppd web link you sent reports that this PPD fails
with
> the message:
> 
> Canon_BJC.ppd: FAIL
>       **FAIL**  BAD ModelName - "," not allowed in string.
>                 REF: Pages 59-60, section 5.3.
The web version is the latest (probably from CVS), using even more detailed
checks than the first shipped one. The shipping version will be update too,
I think, with the next release.
> I'll regenerate the foomatic PPD from linuxprinting.org tonight and
verify
> that my PPD is current.  If so, I'll test with and without the
"," in my
> PPD file and see if that corrects the problem.
Another thought: Could it be a setting on XP, which makes it not accept
"unsigned" driever? Hmm... probably XP would complain about this in
more
uncertain terms.... and likely, the (working) Adobe driver files aren't
signed either....
> As always, thanks for all your time and effort.
> 
> David
Cheers,
Kurt

Hi everyone,
 
yesterday I played a bit with configuring Samba 2.2.8a and CUPS 1.1.18
to get Win2k Pro installing drivers automatically by downloading them
from the server. First I had the same trouble about cupsaddsmb skipping
my printer by posting "No PPD file for printer ..." or similar. This
was
because of CUPS server being configured to avoid access to the server
itself by the proper <Location>-tags in configuration file used Deny
from ...
The "Allow from 127.0.0.1" doesn't satisfy because the connection
was
made as "hostname" with the server's IP, and this one was blocked,
so
cupsaddsmb failed "silently".
 
Then after this trouble was found I still was unable to download some
drivers to windows. The client continued to say that the server doesn't
have proper drivers for download and offered to install one locally. I
tested another while without any success before I simply dropped the
CUPS-PS driver files from CUPS subdirectory, so on next call cupsaddsmb
would use the Adobe PS drivers instead to be installed into share
print$. Afterward everything was fine and I could go to bed after some
terrible hours of analysing ...
 
 
Maybe this helps in your case, too.
 
 
Regards
Thomas Urban