CUPS issues.
I have recently installed CUPS and the appropriate Brother MFC-420CN drivers. Now, my printer shows up on "Modify Printer" settings at http://localhost:631/. However, when I try to print a test page, nothing happens.
I am pretty sure it's worth noting that my printer is not connected to my computer. It's connected to a local area network. However, CUPS lists the device URI as usb:/dev/usb/lp0. That's probably not true as it is not directly to my computer. When I try to change the printer's settings ("Printers" tab > Modify Printer -- from http://localhost:631/); I try to save the settings and nothing happens; the next page simply doesn't load. I took a look in the error log there are many "unauthorized" errors. If that is the case, then why doesn't CUPS just prompt for my username/password? It doesn't seem to do that. |
If the printer is not connected to your machine, you probably don't need CUPS. Printing queue is handled by the printer itself or by the machine it is connected to. What you need to do is to configure it.
If you're using KDE, run kprinter->Add printer. Then choose the right type. If you're unsure, just try the remote ones one by one and one (maybe more) of them should work. |
Quote:
There is only one printer on my network, and I know its IP address, so that should not be a problem. |
Okay, I tried
Code:
$ lp -h http://<ip address of printer>:<printer port> testpage.sxw Code:
lp: Error - scheduler not responding! |
I realized I probably need to omit http:// above. Now I have:
Code:
$ lp -h <ip address>:<port> testpage.sxw |
I recently installed an MFC-425CN on my home network. The Brother website suggests using the driver for the MFC-210C, which works for me.
Go into localhost/631, then Manage Printers, Modify Printer At this point I see MFC-210C. Click "Continue". For Device, select LPD/LPR Host or Printer an click "continue" The URI I use is lpd://192.168.1.2/lpr Adjust address for your network. Use trial and error with ping to locate the printer, or use nmap -sP 192.168.1.* to list the hosts on your network. Use /sbin/ifconfig to get your computer's address. HTH Jim |
I have a similar setup. I use CUPS on several linux hosts, but only one has the printer actually attached. As it happens I also use a 192.168.0 intranet.
First, you need to access the machine that actually has the printer attached. It should be possible to point your browser at "hostwithprinter:631". At that point, you should be able to print a test page. If you can't, then you have a printer printing problem. Look in /var/log/cups (that's on Fedora/Redhat, your mileage may vary). The error_log file may help. Second, on the machine that has the printer physically attached I made these changes to /etc/cups/cupsd.conf. Note 192.168.0.1 is my host with the printer attached Add: Listen 192.168.0.1:631 BrowseAllow from 192.168.0.* BrowseAddress 192.168.0.255 with each of the "Location" sections add: Allow From 192.168.0.0/24 Of course you have to stop/start the CUPS daemon to make these changes active. The changes expose the CUPS server with the printer attached to your internal network. There may be a way to do this with the GUI, but I haven't found it. This works. |
Quote:
Quote:
|
Ah. Perhaps I'm getting closer. The nmap for my printer IP address shows:
Code:
... Code:
$ lp -h <ip address of printer>:515 testpage.sxw |
As usual, it a painfully obvious answer. I should supplied "root" as the username.
Now it works perfectly. I now have a fully functional Linux system! |
You can also use jetdirekt from cups (select device AppSocket/HP JetDirect i Cups webb interface).
I would set up a server for the printer, and then let all other machines use that server. Easier to get controll over the printer then. It also means you only have to manage the printer from one place. No need to install drivers/printers on every computer. It prob. work with all your machines using the printer directly, but... |
Quote:
|
Quote:
This is what I would do in this situation. Run and manage all printers with Cups. This makes it much easier to manage printers (add and remove) for your system. Only one place to manage printers and you are able to distribute queues between many printers and distribute load between different printer server when/if you get problems with printer server hardware. And there IS IPP (Cups) drivers for MS Windows now. Run SAMBA and let that manage printers and file servers for MS Windows machines. This one place to manage recources for you MS Windows machines. You will only need to manage printers in MS Windows machine on one place. Also manage users and file shares on one place. Which is a MAIN boon whith this resolution. Run LDAP or Samba to manage users that are same at each MS Windows klients. You can log in on different machines and have all you files at your fingertips. Yes, you can do this whith MS Windows servers, but why run heavy window environment on a file/printer/user server? And why run an os that is unsecure and unstabel compare to what you can get whith this? |
Quote:
Quote:
|
All times are GMT -5. The time now is 08:29 PM. |