Noon to all

I'm testing Suse 9.3 and got everything set.
What I'm trying to do now is adding a windows printer.
I went through the first screen of CUPS (Name, Location, Description) okay.
When I got to "Select Device", I couldn't find 'smb' (or anything that could be like it), so I picked up anyone.
I added the URI as if it was a smb printer: "smb://...", picked up Make (HP) and the Model (1300 Postscript).
Then I receive a "client-error-not-possible" and the printer is not added.
I download the tarball for CUPS and checked the configure options, but there was nothing like a "samba support".
Before I start compiling things out, is it possible to someone tell me if there's another way around?

I think you need to install the samba-client package with YaST. Then you should find the option "Print via SMB network server" in the printer dialog of YaST.

I had a problem setting up a printer in SuSE. The reason was that cups runs as user "lp".

To configure the printer, I used the "lppasswd" command to add a user and password. I used my username and password so I wouldn't need to remember yet another password. ( You may need a password that has at least one number and is at least 6 characters long ).

If you have apache2 and cups installed, you could point your web browser to "localhost:631"

I believe that you could add a printer using the web interface also.

Hum, so probably it's a samba config?
I have samba compiled, I'm not using the distro packages.
I'll check the samba then.

Hum, nope, that didn't solve it.
I recompiled SAMBA using --enable-cups (first it complained, then I installed cups-devel and everything went fine).
But nope, CUPS still won't show me smb printers, and error_log will still show me the message: "bad device-uri attribute"
I'm really trying to avoid having to compile CUPS as well. Anyone has any other idea?

You probably have your reasons not to use the SUSE package, but I think it is worth trying. Maybe the problem is connected to different paths/structure. You only need to install the client package. It could also be a firewall issue. Did you open the netbios port(s)?

Actually if I use the package from the CD, I'll have to go after its source, because I have a patch to be applied to smbspool.c.
Well, I'll see what I can do.

Should be no problem. Download the src.rpm, patch and rebuild the rpm. Interestingly, I could not find a separate samba-client.src.rpm. But maybe you wouldn't care anyway.

Okay, no problem at all.
A guy at cups.org gave me the solution.

Just copy or link the smbspool (/usr/local/samba/bin/smbspool) to the cups backend directory with the name of "smb" (/usr/lib/cups/backend/smb) and then restart cups.