Samba: Printer works for Windows, but not for Linux
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba: Printer works for Windows, but not for Linux
Hi,
I have a funny problem regarding printer usage in a local network.
I'm using Samba and Cups. Network Shares are working fine, printing is also possible for the Windows Clients in the network. But there's one Linux client which can't find the printer over the network.
The Server is running Ubuntu Server, the client Suse 10.2.
Linux to linux printing is different than windoze to linux printing. You do not need samba to print linux to linux. You could probrbly get that to work, but it is totally unnecessary, and is too complicated.
For linux to linux, install cups on both systems. Get local printing working on the print server. On the client, open the cups web interface with http://localhost:631 and log in as the administrator.
Add the remote printer. The only difficult part is the device URI. As long as you have IP connectivity, the device URI will look like this:
Code:
ipp://192.168.1.21/printers/4039
O.K. the IP address is the IP address of the linux print server, the word 'printers' has to be there, it took me a lot of time to find that out; its in the cups doc, and the last field is the name of the printer on the server.
Use the same print driver on the client as the server. That is it, it should print.
So, now this sounds quite easy. My only problem now is probably quite easy to solve, but I just don't know how to do it.
When I'm trying to access the web interface I get an error, saying :Could not connect to host localhost (port 631).
Apache is running and accessible, local on the server and also via network.
I guess there's some package missing, but I couldn't figure out which.
Did you use http://localhost:631 on the client or the server?
Should be the client.
And Apache dont have to be running the, think cups has its own 'server'
OK, it does work on the client, but not on the server (though I don't know, if that's important anyway).
However I can't add the printer, because I get asked for username and password for the server, and none does work. Also auto-finding via network (using Yast) hasn't worked in the past.
BTW, that apache thing was not meant to have anything to do with cups itself, just wanted to state that there's something there accessible local and over network.
I now have made an experience, which will probably decrease the error-possibilities:
I tried to add the printer on my laptop (running Slackware 10.2). My laptop is finding it without problems, I just do not have any driver to actually use the printer, but even finding was not successful in SuSE.
So I tried again, and got an error message saying that the connection to the cups server failed and that something with searching for IPP had failed somehow.
So I checked if cups is running, but Yast said all cups services are running and also the webinterface is accesible.
So what can I do to make cups running on SuSE as smoothly as on Slackware?
However I can't add the printer, because I get asked for username and password for the server
If you are on the client, it is asking for the password for the Admin on the client, not the server. You don't get asked for the server password on the web interface, unless you used the IP address of the server when you connect to port 631.
Quote:
I just do not have any driver to actually use the printer
What printer is it? Make and model. When cups is installed you also install a lot of drivers. Go here --> http://www.linux-foundation.org/en/OpenPrinting to see if your printer has a known working driver.
Post back the printer information if you can not find one.
If you are on the client, it is asking for the password for the Admin on the client, not the server.
I'm configuring the printer already as root. Asking for the root-password again doesn't make sense, or do you mean something different?
However, somehow I don't get asked for it today (strange behavior, SuSE?).
Quote:
What printer is it? Make and model. When cups is installed you also install a lot of drivers. Go here --> http://www.linux-foundation.org/en/OpenPrinting to see if your printer has a known working driver.
Sorry, you missunderstood me. I have a working driver for the printer (HP LaserJet 1022). It was just not installed on my laptop, when I tested if I could connect to the printer on Slackware.
My problem is that, as I've written before, the printer is accessible from Windows clients. I can also print directly from the server, which is Ubuntu 6.06, and my Laptop is findig the printer without problems, so I guess, if I had a driver installed, printing would also be fine.
There's just a hell lot of errors on the SuSE machine (Have I mentioned that I dislike SuSE?).
SuSE has some problems initializing cups, and does not find the printer on the network.
I'm configuring the printer already as root. Asking for the root-password again doesn't make sense, or do you mean something different?
On the client, you open a web browser, and http://locahost:631 , you get a web page, the top option is "Do Admin Tasks" click that, you will be prompted for a user and password. You can log there as root or admin and provide the correct password. Then you can add the printer.
Have you gone through the printer add on the client, added the printer on the client, and specified the correct driver on the client?
I do not use Suse, so am unfamiliar with any Cups issues on Suse. Have a look on the client to see if cupsd is running. On a konsole enter 'ps aux | grep cupsd' and see if the process is listed.
I've now added the printer via the cups backend, and the same printer, just with another name, via kdeprint.
When I'm trying to print a test page, I get an error saying "/usr/lib/cups/backend/ipp failed".
That is probably the cause, but I have no solution how to solve this!
I've had trouble with this in the past. I had a Windows Virtual machine on a laptop running SUSE --where the Windows Virtual guest machine had no trouble printing to the remote printer running on another SUSE machine.
The HOST however couldn't print.
Finally got it worked out.
On remote machine IP address is 192.168.2.3
For Cups on the laptop to access the printer
device URI is
192.168.2.3:631/printers/stylusphoto1290
(a common mistake here is to forget the :631 in the IP address).
where stylusphoto1290 is the name of the remote printer.
To get it to work initially switch off all firewalls and use the same user name with the same password on the laptop as the remote Linux machine. This stops things like user accounts / password problems interfering with the intial process.
Now just do Print test page.
Should work fine.
If your printer hasn't been installed CUPS will present a reasonable selection of printers to install.
If you can access the remote machine physically at the same time you can look at the printer queue to see if the job as reached the remote printer.
on the remote machine point a browser to localhost:631 and go to the admin screen.
Go back and re-read post number two, you don't have the IPP set up correctly.
Do you mean the setup on the Client, or the setup on the server?
1kyle wrote:
Quote:
If you can access the remote machine physically at the same time you can look at the printer queue to see if the job as reached the remote printer.
on the remote machine point a browser to localhost:631 and go to the admin screen.
At least this one is impossible to me, at this point, as I've written before, I do not have any web interface to cups on the server-side. But thanks for the tip, I'll try it with the kdeprint interface.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.