HP Setup Always Fails On Network Discovery

Asked by KitchM

No matter how many times I run hp-setup, it always fails to find my network printer. I just tried it again with the installer routine, and it was the same.

CUPS has already found the printer and it is working, but hplip fails to. And that means I have not toolbox.

I wish this was fixed.

Xfce on Fedora 17 with Officejet 7000.

Question information

Language:
English Edit question
Status:
Answered
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Amarnath Chitumalla (amarnath-chitumalla) said :
#1

Hi,

Please paste following commands output to analyse further.

$ hp-check
$ ping <IP address of printer>
$ hp-setup -g <IP address of printer>

Thanks & Regards,
Amarnath

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#2

And thank you.

Everything good on hp-check except:
HP_HP_Officejet_7000_E809a
--------------------------
Type: Unknown
Device URI: dnssd://Officejet%207000%20E809a%20%5BBB7C0A%5D._pdl-datastream._tcp.local/
PPD: /etc/cups/ppd/HP_HP_Officejet_7000_E809a.ppd
PPD Description: HP Officejet 7000 e809a Series, hpcups 3.12.11
Printer status: printer HP_HP_Officejet_7000_E809a is idle. enabled since Mon 18 Mar 2013 12:37:36 AM EDT
warning: Printer is not HPLIP installed. Printers must use the hp: or hpfax: CUPS backend for HP-Devices.

ping HPBB7C0A.local/192.168.1.65:80
ping: unknown host HPBB7C0A.local/192.168.1.65:80

hp-setup -g ping HPBB7C0A.local/192.168.1.65:80

HP Linux Imaging and Printing System (ver. 3.13.3)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-13 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

hp-setup[3008]: debug: param=ping
hp-setup[3008]: debug: selected_device_name=None
hp-setup[3008]: debug: Sys.argv=['/usr/bin/hp-setup', '-g', 'ping', 'HPBB7C0A.local/192.168.1.65:80'] printer_name=None param=ping jd_port=1 device_uri=None remove=False
Searching for device...
hp-setup[3008]: debug: Trying ZC hostname ping
hp-setup[3008]: debug: Not found.
hp-setup[3008]: debug: Trying serial number ping
hp-setup[3008]: debug: Probing bus: usb
hp-setup[3008]: debug: Probing bus: par
error: Device not found. Please make sure your printer is properly connected and powered-on.
error: Invalid manual discovery parameter.
hp-setup[3008]: debug: Starting GUI loop...

Done.

Thanks again.

Revision history for this message
Amarnath Chitumalla (amarnath-chitumalla) said :
#3

Hi,

If the Printer IP is 192.168.1.65, please try following.

$ ping -c 3 192.168.1.65
--> If this command is successful, run hp-setup

$ hp-setup -g 192.168.1.65

Thanks & Regards,
Amarnath

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#4

Okay, that worked!

Too bad that the hp-setup couldn't find the printer that CUPS and avahi could. That is what most people would consider a flaw in the program. I would like to see that fixed.

Also, I would like to see the application work without needing to install unneeded dependencies, such as for scanners and such.

In any case, thank you very much for the manual work around. I now have the toolbox.

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#5

Thanks Amarnath Chitumalla, that solved my question.

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#6

Now I have Fedora 19 and the installation program says it is not supported. However, it ran as Fedora 18 and completed correctly.

But, the recognition of the network printer failed, until I selected SLP.

Why can't the software detect the existing network printer in the first place?

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#8

So, what is going on with this software problem? Obviously, the software needs to do network discovery. Will that be fixed soon?

Revision history for this message
Sanjay Kumar (sanjay-kumar14) said :
#9

Hello KitchM,

SLP is now the default discovery protocol in HPLIP-3.13.8.

Thanks,
Sanjay

Revision history for this message
KitchM (tech-frontrowcomputer) said :
#10

Thanks, Sanjay.

That will be a good start. However, the real issue should be that no method of communication is left out of the process. The program needs to scan completely thru all normal types of connectivity, or there will always be something left out. The user should not have to guess at which type they need to select.

Thanks again.

Can you help with this problem?

Provide an answer of your own, or ask KitchM for more information if necessary.

To post a message you must log in.