Author Topic: device communication error (5012) (Solved)  (Read 7906 times)

Offline rick0612

  • Sr. Member
  • ****
  • Posts: 258
  • The only dumb question is the one not asked.
Re: device communication error (5012)
« Reply #15 on: January 18, 2011, 05:35:10 PM »
Sees no printers at all, none, nada, not even one. In fact, Printerdrake doesn't look at the network for some reason.
Packaging rig: Averatec 2573 /12.1" screen /2.0GHZ /3GB RAM /120GB SSD /Minime 2012.12

Daily rig: Alienware X51 /23" monitor /Windows 7 host /KDE VBox client

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: device communication error (5012)
« Reply #16 on: January 18, 2011, 06:59:58 PM »
Rick;

I am pretty sure you already tried this, but what happens if you un-check auto-detection on the Printerdrake wizard?

Also, now that Printerdrake is installed, go to Configure Cups, and make sure that the top button says "Remote Cups Server  and no local Cups daemon: Off. 
« Last Edit: January 18, 2011, 07:07:45 PM by GermanTux »

Offline rick0612

  • Sr. Member
  • ****
  • Posts: 258
  • The only dumb question is the one not asked.
Re: device communication error (5012)
« Reply #17 on: January 19, 2011, 03:54:02 PM »
Tried another route.

Backed up my home folder, removed Virtualbox 4.0 and all vdis, installed Virtualbox 3.2. Did clean install of Minime 2010.12. Still no printer.
For the heck of it, I installed the printer in the Windows host and it installed and works fine.
I believe it may be a Windows 7 Home Premium problem. I haven't messed with Windows in so long, I have no idea where to start.

Is there a way to access the printer on the Windows host? I'll be investigating that route.

Thanks for all the inputs.
Packaging rig: Averatec 2573 /12.1" screen /2.0GHZ /3GB RAM /120GB SSD /Minime 2012.12

Daily rig: Alienware X51 /23" monitor /Windows 7 host /KDE VBox client

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: device communication error (5012)
« Reply #18 on: January 19, 2011, 06:33:17 PM »

Is there a way to access the printer on the Windows host? I'll be investigating that route.

Thanks for all the inputs.

Yes, but it still involves installing the Linux driver.  First, share the printer under Windows.  Then, in printer drake, select network printer, then SAMBA host.  Good luck...Cannot say I've run into such a strange problem before.