SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
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 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, 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)?