Comment 8 for bug 521909

Observations consistent with previous posters. Same problem here with hplip 3.11.10 and Debian squeeze on a wired ethernet install of Officejet 7000. Worked previously with a CUPS install, but I wanted ink-level reporting with hplip. Repeated install tries with hp-setup gave "unable to communicate with device (code=12)." Solution or workaround came from a search that gave the suggestion for hp-setup of >show advanced options>manual discovery>show device URI with ip not zc. The ip came from the Network Configuration Page printed from the printer, so the network was up and known by the printer. This proves that this is a hplip software problem, at least to me. Perhaps start avahi-daemon would work for me, but this is beyond my current skill set.