[cups.general] printer not found and no manual option apparent

[Michael Sweet]

More than likely the issue is just that the 175 does not support SNMP or has the wrong network configuration (and so isn't responding to the broadcast address(es) used by your computer...)

What do you see if you print a configuration page from the JetDirect?

On Dec 19, 2011, at 2:37 AM, Paul Douglas wrote:
> I'm running CUPS 1.5.0 on FreeBSD.  My old Laserjet 4500N (accessed via network) was detected and installed easily using the Search For Printer function.  I have now swapped that for a Laserjet 1200 accessed via a Jetdirect 175.  When I try the Search or Add functions, CUPS responds that no printer is found.
> 
> I have a couple of linux boxes and have tried the printer via those and both detect it and allow me to install it and print to it.  The only difference I am aware of is that they both have slightly older versions of CUPS on them, eg one has 1.4.4.
> 
> I have looked at the debug output from backend/snmp and all the computers I have tried seem to get the same response from the printer, ie that it is a printer and its IP address is x and it is not responding with an actual device name or type.
> 
> The behaviour that is different is that on the 1.4.n CUPS I am taken to the manual configuration page that allows me to choose make, model and driver for the printer, but the 1.5.0 simply says No Printers Found and will not, so far as I can tell, allow me to configure it manually.  Is this something that has been removed from this later version of CUPS so that I could solve the problem simply by going back to an earlier version?
> 
> The output from backend/snmp is as follows:
> 
> CUPS 1.5.0 on FreeBSD:
> 
> . 
> DEBUG: IN Message:
> DEBUG: IN SEQUENCE 41 bytes
> DEBUG: IN     INTEGER 1 bytes 0
> DEBUG: IN     OCTET STRING 6 bytes "public"
> DEBUG: IN     Get-Response-PDU 28 bytes
> DEBUG: IN         INTEGER 1 bytes 1
> DEBUG: IN         INTEGER 1 bytes 2
> DEBUG: IN         INTEGER 1 bytes 1
> DEBUG: IN         SEQUENCE 17 bytes
> DEBUG: IN             SEQUENCE 15 bytes
> DEBUG: IN                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.2.1
> DEBUG: IN                 NULL VALUE 0 bytes
> DEBUG: 0.006 Received data from 192.168.1.9...
> DEBUG: community="public"
> DEBUG: request-id=1
> DEBUG: error-status=2
> DEBUG: add_cache(addr=0x7fffffffc568, addrname="192.168.1.9", uri="(null)", id="(null)", make_and_model="(null)")
> . 
> [then several repeats of attempt to establish printer info:]
> 
> DEBUG: OUT Message:
> DEBUG: OUT SEQUENCE 43 bytes
> DEBUG: OUT     INTEGER 1 bytes 0
> DEBUG: OUT     OCTET STRING 6 bytes "public"
> DEBUG: OUT     Get-Request-PDU 30 bytes
> DEBUG: OUT         INTEGER 1 bytes 4
> DEBUG: OUT         INTEGER 1 bytes 0
> DEBUG: OUT         INTEGER 1 bytes 0
> DEBUG: OUT         SEQUENCE 19 bytes
> DEBUG: OUT             SEQUENCE 17 bytes
> DEBUG: OUT                 OID 13 bytes .1.3.6.1.4.1.641.2.1.2.1.3.1
> DEBUG: OUT                 NULL VALUE 0 bytes
> DEBUG: OUT Hex Dump (45 bytes):
> DEBUG: OUT 0000: 30 2b 02 01  00 04
> .. etc
> 
> followed by responses from the printer that continue only to give the same limited info:
> 
> ..
> DEBUG: IN Message:
> DEBUG: IN SEQUENCE 43 bytes
> DEBUG: IN     INTEGER 1 bytes 0
> DEBUG: IN     OCTET STRING 6 bytes "public"
> DEBUG: IN     Get-Response-PDU 30 bytes
> DEBUG: IN         INTEGER 1 bytes 6
> DEBUG: IN         INTEGER 1 bytes 2
> DEBUG: IN         INTEGER 1 bytes 1
> DEBUG: IN         SEQUENCE 19 bytes
> DEBUG: IN             SEQUENCE 17 bytes
> DEBUG: IN                 OID 13 bytes .1.3.6.1.4.1.128.2.1.3.1.2.0
> DEBUG: IN                 NULL VALUE 0 bytes
> DEBUG: 0.037 Received data from 192.168.1.9...
> DEBUG: community="public"
> DEBUG: request-id=6
> DEBUG: error-status=2
> DEBUG: 2.037 Scan complete!
> 
> 
> CUPS 1.4.4 on Debian:
> 
> only one output message, much as above and not repeated here, followed by only one input message, also mush as above but here it is anyway:
> 
> . 
> DEBUG: IN Message:
> DEBUG: IN SEQUENCE 41 bytes
> DEBUG: IN     INTEGER 1 bytes 0
> DEBUG: IN     OCTET STRING 6 bytes "public"
> DEBUG: IN     Get-Response-PDU 28 bytes
> DEBUG: IN         INTEGER 1 bytes 1
> DEBUG: IN         INTEGER 1 bytes 2
> DEBUG: IN         INTEGER 1 bytes 1
> DEBUG: IN         SEQUENCE 17 bytes
> DEBUG: IN             SEQUENCE 15 bytes
> DEBUG: IN                 OID 11 bytes .1.3.6.1.2.1.25.3.2.1.2.1
> DEBUG: IN                 NULL VALUE 0 bytes
> DEBUG: 0.014 Received data from 192.168.1.9...
> DEBUG: community="public"
> DEBUG: request-id=1
> DEBUG: error-status=2
> DEBUG: 2.016 Scan complete!
> 
> 
> In all cases I am accessing CUPS via its http interface (localhost:631) not any kind of OS specific tool.
> 
> Any suggestions much appreciated,
> 
> Thanks - Paul
> 
> 
> _______________________________________________
> cups mailing list
> cups at easysw.com
> http://lists.easysw.com/mailman/listinfo/cups

__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair