I've received the following mail related to this issue:
> HPLIP's tools like hp-toolbox do not support this kind of
> network connected printers, see
> http://hplipopensource.com/node/286
> -------------------------------------------------------------------
> Does HPLIP support networked printers?
> Answer:
> Yes, HPLIP supports printers that are directly network connected
> (via a built-in Ethernet port) or connected to a network
> via a JetDirect.
> -------------------------------------------------------------------
> and
> http://hplipopensource.com/node/287
> -------------------------------------------------------------------
> What network print servers are supported?
> Answer:
> Currently we have only tested HP JetDirect devices with HPLIP.
> No other network print servers are supported.
> -------------------------------------------------------------------
>
> What you do is network printing via CUPS and this limits the
> supported functionality to what is provided by CUPS.
>
>
> For example if a HP all-in-one device was connected as you do it,
> you could not use its scanner unit with HPLIP's tools from the
> remote machine but you could set up "Scanning via Network" see
> http://en.opensuse.org/SDB:Configuring_Scanners_from_SUSE_LINUX_9.2
> which results scanning via network via SANE and limits the
> supported scanning functionality to what is provided by SANE.
>
>
> To use HPLIP's special functionality from a remote machine you need
> to have the device "directly network connected" as described above.
>
> The reason behind is:
> HPLIP's special functionality (e.g. get the device status - do not
> confuse the actual device status with a remote print queue status)
> needs a direct bidirectional communication with the device
> and not whatever kind of indirect communication.
>
>
> Kind Regards
> Johannes Meixner
I've read pages on hplipsource.com and I still insisting that that behavior
like this is certainly HPLIP's bug.
I think that HPLIP should give more descriptive error message at least.
And it's certainly shouldn't show tons of useless popup notifications.
I've received the following mail related to this issue:
> HPLIP's tools like hp-toolbox do not support this kind of hplipopensource .com/node/ 286 ------- ------- ------- ------- ------- ------- ------- ------- ---- ------- ------- ------- ------- ------- ------- ------- ------- ---- hplipopensource .com/node/ 287 ------- ------- ------- ------- ------- ------- ------- ------- ---- ------- ------- ------- ------- ------- ------- ------- ------- ---- en.opensuse. org/SDB: Configuring_ Scanners_ from_SUSE_ LINUX_9. 2
> network connected printers, see
> http://
> -------
> Does HPLIP support networked printers?
> Answer:
> Yes, HPLIP supports printers that are directly network connected
> (via a built-in Ethernet port) or connected to a network
> via a JetDirect.
> -------
> and
> http://
> -------
> What network print servers are supported?
> Answer:
> Currently we have only tested HP JetDirect devices with HPLIP.
> No other network print servers are supported.
> -------
>
> What you do is network printing via CUPS and this limits the
> supported functionality to what is provided by CUPS.
>
>
> For example if a HP all-in-one device was connected as you do it,
> you could not use its scanner unit with HPLIP's tools from the
> remote machine but you could set up "Scanning via Network" see
> http://
> which results scanning via network via SANE and limits the
> supported scanning functionality to what is provided by SANE.
>
>
> To use HPLIP's special functionality from a remote machine you need
> to have the device "directly network connected" as described above.
>
> The reason behind is:
> HPLIP's special functionality (e.g. get the device status - do not
> confuse the actual device status with a remote print queue status)
> needs a direct bidirectional communication with the device
> and not whatever kind of indirect communication.
>
>
> Kind Regards
> Johannes Meixner
I've read pages on hplipsource.com and I still insisting that that behavior
like this is certainly HPLIP's bug.
I think that HPLIP should give more descriptive error message at least.
And it's certainly shouldn't show tons of useless popup notifications.