Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Something went wrong during packets transmission or on the other side of the communication since I'm almost sure that all was done good and that the Linux printer system (CUPS) is doing well its job.
Maybe the printer cannot accept the job but cannot communicate to the Linux printer system or vice versa.
Is there any kind of firewall?
yes there is a firewall, and more than one actually, but I have been told it is set to allow all on my lan, which is where my printer is.
Could I use a tool such as nc to see what's wrong ? If so, could you guide me through it? I've never used it before.
Actually I tried tcpdump and what I find out is that my computer seems to sends the following sentence to the printer, instead of the file content:
**** Unable to open the initial device, quitting.
Does that help to figure out what's wrong ?
Well I did and it doesn't work either. It still produces no error, goes to the print queue and then gets out of it as though it was printed, but the printer still doesn't print anything. This time, tcpdump doesn't produce any understandable ascii message. If that helps, the tcp flow is as follow: syn, syn-ack, ack + psh-ack, ack + psh-ack, ack + ack + ack + psh-ack, ack + ack + ack (tcp window update), psh-ack, ack + fin-ack, ack+fin-ack, ack.
okay I did, it's still exactly the same. The queue is emptied, but nothing is printed.
edit: oh and by the way this configuration file said that I should not modify it if cupsd was running, so I tried to kill it, but it spawned right back, so I did the modifications with cupsd running.
There is no /etc/rc.d directory in my 12.04 ubuntu, nor any rc.cups file in the /etc/ folder, or any of its sub folder.
In any case, I rebooted the computer, which would restart that daemon, and the printer still doesn't print anything, so the modification we made in the /etc/cups/printers.conf file didn't solve the problem.