device communication error (5012) (Solved)

[rick0612]

Hi

My Linux install no longer communicates with my HP7210 AIO. Let me explain.

I was running PCLOS 2010 as a client in virtualbox 3.2 on a Windows XP host. Everything worked perfectly even the network connected HP AIO.

I exported the VM as an appliance and imported it into my new PC with Windows 7 Home Premium and Virtualbox 4.0. Everything works perfectly except the printer. I cannot even install it. The HP setup app sees the printer but when I click next, I get device communication error (5012).

I tried reinstalling everything printer related including cups. I even tried changing the network adapter because I got scanning to work in Virtualbox 3.2 by changing from NAT to Bridged. So far nothing doing.

Any ideas would be greatly appreciated.

Thanks

Solution: The printer installed with terminal command: hp-setup -i 192.168.xxx.xxx
This command bypassed the GUI setup which I think was timing out before the printer could respond. (Windows 7 probably has something to do with that.)
Don't have the scanner part of the AIO yet. That will be another post perhaps.

Thanks for all the replies, especially Germantux

[smcs_steve]

Try a printer reset?
Remove the power cord from the back of the unit.
Press and Hold the # and 6 button and plug in the power cord.
this will reset the printer.
>Steve

[rick0612]

Steve

Thanks for the response. I should have mentioned before that the printer and scanner work perfectly from other PCs. My bad.

Rick

[GermanTux]

Rick;

This sounds like a networked printer, correct?  Can you ping it from the PCLOS host? 

Also, I am a little confused.  How did you re-install the driver?  And from your wording, I an interpreting it that you are running Windows 7 at your O/S, and PCLOS as a guest O/S inside Virtualbox.  Is this correct?  Make sure the firewall in Windows 7 is off.  Do this by disabling the Windows Firewall service (set the service to disabled).  Do not try and do it through the Network Settings in the Control Panel.  It has habit of re-enabling itself. 

Go to Control Center->Hardware->Setup up print queues and DELETE the printer.  Then reboot PCLOS, and try going back there and setting it back up.  See if that works. 

[rick0612]

German Tux,

Thanks for the reply.

Yes the printer is connected to the home network. I can use Firefox from within PCLOS client on the Windows 7 host machine and connect to the printer. I can browse settings, status, etc in the printer's web site.
Windows 7 firewall is off and has been.
The printer was originally set up and running in the PCLOS Virtualbox client on the Windows XP host machine. I moved the vdi to the new computer but the differences are: Virtualbox old 3.2 vs new 4.0, old Windows XP host vs new Windows 7 host.
Everything works perfectly, networking, Firefox, Thunderbird, etc. The first time I tried to use the printer, I got the Device communication error. I uninstalled the printer. When reinstalling, the HP setup app discovers the network printer but when I click next, it sits for a long time then gives this error: "Unable to communicate with the device. Please check the device and try again."
I'm thinking it has to be something with virtualbox because it worked great in 3.2 but fails in 4.0.

Rick

[GermanTux]

OK, that clears things up.  Unfortunately, it sounds like you've got a hell of an issue there.  

Delete the printer.  Then - re-install the package task-printing-hp.  Open a terminal as root:

apt-get --reinstall install task-printing-hp.  

Then try adding the printer again.  

If that fails, setup another vbox virtual machine with either PCLOS or another distro (doesn't matter which, as long as it has an easy utility to add printers).  Depending on what happens there, that will tell us if it's Virtaulbox 4, or the VM itself.  

I will try and install virtaulbox 4 tomorrow to see if they added any new network options that might be holding you back.  Admittedly, I have not toyed with the new version yet.  

[rick0612]

Started new vm with PCLOS Minime 2012
With same Virtualbox 4.0 on same Windows 7 host
Did all upgrades
Rebooted
Installed task-printing-hp from Synaptic
Rebooted
Ran Setup Device in HP Manager
  Discovers printer
  After clicking Next, long wait then "unable to communicate with device" error
For the heck of it I tried printing from Kwrite and it worked
HP Manager reports no device still and wants to install; endless loop
Tried installing scanner but cannot install packages from PCC -> Hardware -> Set up scanner
Installed saned and xsane from Synaptic other sane packages were already installed
xsane reports no devices available
Went to HPLIP website but they are temporarily offline. Will try them again later, maybe they have an answer

[Texstar]

I'm not sure with using windows as host but with linux as a host I had to install their extension pack in order to enable usb support.

[rick0612]

Thanks Texstar,

This is a network connected printer.

[smcs_steve]

rick0612,
At the Win7 end did you set your printer as shared, and allow W7 share access without password permissions?
(I'm assuming you are connected to LAN and have VBox network set to bridged)
>Steve

[GermanTux]

rick0612,
At the Win7 end did you set your printer as shared, and allow W7 share access without password permissions?
(I'm assuming you are connected to LAN and have VBox network set to bridged)
>Steve

Steve, this is a direct IP printer.  The VBOX host is communicating directly with it. 

Rick, I wish I had better news for you, but it sounds like a driver issue.  The strange thing is it was working under VBOX 3.2... 

One last thing to try - choose a new network card for your VM.  do this by going into machine settings->network->advanced, select PCNET II.  Secondly, go to Control Center->Hardware->Printers->Actions->Configure CUPS.  Make sure the CUPS daemon is off. 

I also do not see the printer on HP's compatibility list....

[rick0612]

German Tux,

I have already gone through all the possible combinations of NAT or Bridged and all the network cards available. No luck.

You mention PCC -> Hardware -> Printers. I don't have the Printers option in my setup; neither the original vm nor the second vm I setup to test with. Never have had that option with Minime, I don't think. Maybe that's a full KDE option? Why would we want to shut off the cups daemon, don't we need that for printing?

As far as compatibility, I've been running this printer for years in PCLOS and there is a .ppd file for it in the hplip package.

As a further note; when I tried to install the printer in the test vm, I canceled the install when I got the no communication error. I didn't complete the install but the printer worked. Right now I can print but sane says there is no scanner, and HP Device Manager says there is no printer.

[GermanTux]

German Tux,

You mention PCC -> Hardware -> Printers. I don't have the Printers option in my setup; neither the original vm nor the second vm I setup to test with. Never have had that option with Minime, I don't think. Maybe that's a full KDE option? Why would we want to shut off the cups daemon, don't we need that for printing?

OK.  Install printerdrake then in Synaptic.  That should make the printer/scanner item show up inside the Control Center. 

Of note, I tried installing Printerdrake inside the XFCE minime, and it still did not show up.  Hopefully, that is not the case in the KDE MiniMe version.

[rick0612]

Tried Printerdrake but it does not recognize network printer even though I told it that was where to look. Inputting the IP address was no help.

Printerdrake did show up in PCC.

Continuing search for solution. 

[GermanTux]

Rick;

So it does not give you the option to select what printer your model is?