Network printer fails to print.

[joseppi]

After posting this topic in "General" someone suggested reposting the problem here.

Why do documents that cups reports as sent successfully vanish and not get printed?
Please refer to the six screen captures shown in the following two image at these links:
http://upquick.com/temp/cups.jpg
http://upquick.com/temp/cups2.jpg

The subject printer is turned on, set-up, and documents sent wirelessly from my wife's win-xp laptop to the printer print successfully, but documents that I send to print from my linux machine just vanish.

See the previous topic submission here:
http://www.pclinuxos.com/forum/index.php/topic,108430.0.html

[Grandpa]

When you set the printer up did the computer find it?  Did you tell the computer what IP address to look for?

[joseppi]

Yes, the computer found the printer (as shown in the second set of screen captures).
How can I tell the computer what IP address to look for?
I can't find any option to do that in the PCC printer settings.

[Grandpa]

It has been a long time ago like I said before.  But I am thinking that when I was setting it up I told it where to look for it.  Seems like you could either let the computer search for it or tell it where it was.  Sorry I can't be more help.  BTW I don't use it wireless any more.

[wedgetail]

joseppi
What OS are you using?

Post the output of lpstat - t, from a konsole:

lpstat -t

I have looked at your references and all seems to be fine. 

Your print job counter is up to 276, this begs the question when did this start?  Has it been printing fine before certain action/date/updates?

You have not said if your pc also prints Wirelessly, but I make the assumption you do  because if it was a wired cabled network connection I would expect an alarm message.  

I don't know the printer and I am not very familiar with wireless networked printers and the CUPS message system.  It will have to be a bit of learning for me here, so will start with the lpstat information.

[joseppi]

> What OS are you using?

PCLinuxOS with the latest updates on two of my computers and the most current Kubuntu one other.

> Post the output of lpstat - t ... results:

scheduler is running
system default destination: Canon-MX430
device for Canon-MX430: dnssd://Canon%20MX430%20series._printer._tcp.local/
Canon-MX430 accepting requests since Fri 24 Aug 2012 01:26:31 PM MST
printer Canon-MX430 is idle.  enabled since Fri 24 Aug 2012 01:26:31 PM MST

> ... when did this start?   Has it been printing fine before certain action/date/updates?

This is a new Canon printer that works fine when printing wirelessly from my wife's win-xp laptop,
but I it does not print when I send a document to it from either of my 3 Linux systems. 

> You have not said if your pc also prints wirelessly, but I make the assumption you do
> because if it was a wired cabled network connection I would expect an alarm message.

Printing works fine from each of my three Linux computers (one wirelessly from a laptop) to my old  HP LaserJet 4 printer that is ethernet connected to my oldest Mandriva Linux computer.

[CaptainSarcastic]

Have you installed the Canon printer packages in Synaptic?

I just checked by searching on "Canon" in Synaptic, and while I show task-printing-canon installed, there are a number of Canon printer drivers which do not show as installed.  Might be worth double-checking on your system.

I don't have a Canon printer myself, so never checked it before.

[wedgetail]

joseppi
Ah, yes I did get a bit tripped up, it is the first time I have actually noticed somebody using a dnssd connection as in the line from lpstat -t:

device for Canon-MX430: dnssd://Canon%20MX430%20series._printer._tcp.local/

I can do some guessing but I am better off saying I don't know anything about the internals of this protocol, I know the normal ethernet cable connections and direct USB and parallel port connection fairly well. Using this protocol is also the reason why you do not see any IP address associated with your printer when doing an lpstat -t

To me it is likely this is the part of the problem.  How to fix it is another matter.  I can possibly diagnose a bit closer what is happening on the dnssd protocol but would prefer some other more knowledgeable member having a go.  

Edit:
Initially I suggested setting up or adding a new printer connection using ipp://... protocol but I have changed my mind.  The process to be slightly different and using a soket://... protocol.
A simple solution might be if you can change to another protocol. Can you try and set up a socket://... connection? this will involve an IP.  I can only suggest the use of the CUPS web interface, start with clicking on following line::

http://localhost:631/admin

Then Find New Printers this may be the tricky part as you may be presented with 4 options, I am hoping the top 3 looks identical and they are probably dnssd:// protocol. The best is checking each one and hope there will be one that says socket://....  You will need to know the IP address of your printer.

Whilst it is a good suggestion, I repeat I have no practical experience with wireless printers, (I do with printing over the internet cable connected printers using wireless pc connections to my router,  slightly different set up.  It is working on a WiFi connected pc,  I have my information above by checking out setting up another printer queue working over a WiFi path to my router. The printer is cable wired to my LAN and connects to a switch box.  

It bothers me that your hp printer does not show up in the lptstat -t, are you using two different subnet LANs or was the printer and pc just switched off when you did the lpstat?

[malc]

I had problems with a canon mp540 and found out the following two things:

1. The gutenprint drivers did not work very well, instead I downloaded drivers from the canon website. NB on each Client linux machine

2. i defined a printer on the client linux machines with the following protocol to match windows :

Device URI : smb://<IP address>/<printer name>

This is almost identical to windows network printer URL:

//<IP address>/<printer name>

You end up with two CUPS queues one being the printer (server) queue and the second being the linux client printer queue.