Can't Print - OpenSuse 12.3_64 Canon MF5950dw

I have a recent install of OpenSuse 12.3 64 bit which I have kept up to date. My printer is a Canon MF 5950dw. I downloaded the driver files from Canon and used #rpm -ivh
to install them. No problems (referring to a recent thread, I have libtiff5 installed). The printer is wired as a network printer with a static IP address (192.168.1.32).

Here is what happens now: I go into Yast2/Printers
In Printer Configuration the printer named "Canon_MF9500_Series is listed.
I click Edit
In the “connection” window, Mode: “Current Connection:” Connecton: http://192.168.1.32/queue Description "Canon Canon MF9500 with driver Canon MF9500 Series UFRII LT ver.2.5
At the bottom of this screen, the printer is selected as “default” “Accept Print Jobs” and “Enable Printing” I click OK.

So, I go into the “connection wizard” in YaST2. Since this is a network printer, I skip the “directly connected device” section. I choose any of the options in “Print via print server machine” and click on “Look Up” to try to find a host, but none can be found.

So, what have I missed? How can I fix it so that I can print??? If I haven’t given enough information to solve help you help me, what more can I provide?

Many thanks,

Mark

The only suggestions I can offer here is to try

  1. Can you at least ping your printer okay?

  2. Configuring with the firewall disabled temporarily. Depending on the network protocol used, it may prevent the printer being discovered, if a port is being blocked for example.

  3. Configuring manually via the CUPS web interface using your browser:

http://localhost:631/admin

Select ‘Add Printer’ (enter your root credentials when prompted). I’m not sure which network printing protocol this printer supports (proprietary or standard CUPS protocols), but you could try the LPD option with a URI like this:

lpd://192.168.1.32/L1

Thank you for the suggestions. At this point, I can successfully ping the printer. The lpd:// address gave me nothing.(chrome switched to search mode.) For giggles, I entered the address of the printer into a browser and got to the printer’s “Remote UI Portal”, which was not useful, but it tells me that the network is OK. I’ll try disabling the firewall and see what that gets me. I was running Mepis 11.0 before going to OpenSUSE, and the printer worked under that debian derivative, so I know that this is possible.

Again, thanks a lot.

Mark

Did you read the Instructions, that are in the downloaded Canon-File?

I think the main issue is getting the URI correct for network printing. Without owning a Canon printer, I’m not sure which network backend the UFRII driver supports. It would have been useful to keep a copy the working /etc/cups/printers.conf from your Debian install. That would contain the URI.

Try simplifying the lpd:// URI to just

lpd://192.168.1.32

FWIW, here’s the CUPS documentation concerning the standard network protocols:

Using Network Printers - Documentation - CUPS

Hopefully, a user with a similar network-attached Canon printer can chime in.

Another LPD URI possibility worth trying (assuming 192.168.1.32 is printer IP address):

lpd://192.168.1.32:515/queue

I’ve found time to trawl through a variety of threads dealing with connecting to problematic Canon printers (in a network environment). Here’s a Mac thread where, it is suggested to turn on SNMP, before configuring the printer. Now OS X uses CUPS (with same UFRII driver in use), the printer is a similar model, so I’m hoping the same methodology will apply to your situation (refer post #6 in that thread):

I resolved it, after much frustration, by doing the following:

  1. Turned DHCP Auto off
  2. Manually entered IP 192.168.1.XXX
  3. Manually entered Subnet 255.255.255.000
  4. Manually entered Gateway 192.168.1.1
  5. Turned SNMP ON
    6 Most importantly, I re-entered the SNMP Community name back to default - which is “public” all lower case

You could try discovering the printer by running the snmp backend manually like this

/usr/lib/cups/backend/snmp 192.168.1.32

and note what is reported. (CUPS should be able to do this automatically.)

Thank you for the help. Shutting off the firewall allowed me to configure the printer. It now works, and I’m happy.:wink:

That is good to hear. Just a matter of opening the relevant ports for discovery then.

For a complete picture, I’d still be interested in knowing the working URI for your printer (located in /etc/cups/printers.conf). If you have time please post here.