That will be due to the Smart Install 'feature' enabled in the printer. Until you can inhibit that, your printer device won't be available to be detected. Proof of this is that running the CUPS usb backend manually should normally enumerate the USB-attached printer device...

I still don't get why you haven't been able to disable Smart Install via Windows....

https://h30434.www3.hp.com/t5/Printe...w/td-p/6262621

Odd that Launfal doesn't mention this in his 1102w instructions. He says it just worked from day 1.
I didn't try those procedures. If you posted that link before, I'm sorry I missed it.

I'm in the process of reinstalling Linux from scratch because I don't know what I've messed up with trying various things. I'm also going to re-install the Windows VM from an actual installation disk and not from an image restore -- which I suspect is a big part of the problem what with USB devices appearing and disappearing rather randomly. I'll try that disable Smart Install from there.

Coupla questions you may not know the answers to:

1. That link is a howto for Windows 10. Do you suppose it will work for Windows 7?

2. In case this printer gets moved to a different person's workstation one day, is it possible to re-enable the smart install?

I can only speculate here - perhaps it was disabled to start with.

I'm using Windows 7 and in an effort to assist I was able to execute it ok. It launched with a GUI successfully.

I doubt if anyone would want (or need) to use this feature ever. (However, the HP utility can be used to re-enable it if desired.)

OK! All is working (for now)! Here's what I did. ferrari is right (post #32). Smart Install needs to be disabled first or CUPS will never see it as it apparently detects as a CDROM, not a printer. The link ferrari provided: https://h30434.www3.hp.com/t5/Printe...w/td-p/6262621, has the necessary disabling program, something I've been looking for since the beginning. That page has a download for http://ftp.hp.com/pub/softlib/softwa...SI_Utility.exe. When run on a Windows 7 (or Win10) host it let's you disable and enable the Smart Install feature. Important note: this must be run on a REAL Windows computer, not a virtual machine! On a virtual machine it does nothing as that machine does not see the printer either. I suspect the reason is that the physical USB port is owned by Linux and is "given" to the VM through VM configuration, but in the end the VM also thinks it's been given a CDROM, not a printer. Anyway, disabling Smart Install using this utility on a physical Windows 7 host did work.

What I want is for this printer to be served by the Linux host and shared to the Windows Virtual Machine. The Linux host will be up all the time, but the VM may not be. Back on the Linux host, HPLIP still gave me the "Smart Install Device(s) Detected" message, but I ignored that to start with. I went to CUPS which now DOES see the printer! I configured the printer using the standard 1102w driver which was annotated "requires proprietary plugin". However, printing a test page did not work. I still got the "Filter Failed" message.

Next, I deleted the HPLIP package per Launfal's recommendation (which got rid of the "Smart Install Device(s) Detected" message), marked the printer as Shared and installed foo2zjs (http://foo2zjs.rkkda.com/). Then, in CUPS, I selected the HP-LaserJet_Pro_P1102w foo2zjs-z2 (no mention of plugin!). Tada! This finally worked! Yeah!

Since I want the Windows VM to access this printer I followed the instructions in https://wiki.archlinux.org/index.php...Windows_client on setting up a Linux Server - Windows Client. There are instructions on making the printer shared and visible on the network using CUPS. Basically, in Administration > Server > Advanced I checked "Share printers connected to this system". Since my VM has a 10.0.0.0/24 IP and my LAN is 192.168.0.0/24, I also checked "Allow printing from the Internet" which, I assume, permits connections outside the LAN scope.


Back on the WIN7 VM, I made sure IPP was enabled in Control Panel > Programs > Turn Windows features on or off > Print and Document Services. Then, Devices and Printers > Add Printer > ... > The printer that I want isn't listed > Select a shared printer by name. I entered "http://linuxhostname:631/printers/printerShareName". The link ferrari gave also lets you download a Windows driver for the 1102w, but that's an .exe file and I'm pretty sure you can't use it in the "Have Disk" option. So, I selected a generic HP PCL5 driver from the list. That driver would be useful if the printer was hosted on the Windows machine.

And voila! It all worked!

Thanks all for your help. I couldn't have figured this out without LQ. I hope this ordeal and solution can help other poor schmucks in the future trying to get this demon printer working in Linux.

3 members found this post helpful.

Great! Glad to see you finally got this thing nailed!

I'm baaaack, with more troubles on my 1102w demon printer. I'm hooking this Linux box into the Domain for production. As such, it is getting assigned a new IP. The Windows 7 1102w config had the printer address as http://192.168.0.174/printers/HP_1102w. Now the host is CCARTER, or 192.168.0.60. I removed the Windows 7 1102w printer and readded it following exactly the procedures I listed in my preceding post. I've tried using both the CUPS server host name and IP address: http://ccarter:631/printers/HP_1102w. The WIN7 apparently communicates OK with the CUPS server, but the print job is stalled on the Linux end. Showing jobs for that printer in CUPS says, "Name: Unknown, User: Withheld, Size: 43K, State: pending since Mon 29 Jan 2018 07:27:18 PM EST". The log files have:
Any idea what could be wrong? This all worked beautifully a few days ago.

Just in case this is relevant:
https://superuser.com/questions/3009...ows-7-ultimate
In particular...

Yeah, I saw that too, but I don't think that's the problem. Windows does detect the printer just fine, whether I use the CUPS server host name or IP. It does send the test page to the CUPS server, so it's not an issue of Windows being able to detect the printer on the host. The problem is that CUPS has the request queue, but the status is "pending", so it won't print the file!

Why is it "Missing printer-uri"? Why was it not missing this last week? All I've done on the host is change its IP address. I'm ready to go "Office Space" on this printer!

Nevertheless, I'll try your suggestion when I'm back in the office tomorrow.

Check this blog out:
http://notallmicrosoft.blogspot.co.n...eue-fails.html
Specifically, it refers to this Windows hotfix
https://support.microsoft.com/en-nz/...e-is-set-to-is

Thanks, I'll check this out too. Although, still not convinced the problem is on the Windows side. Another suggestion I found said to try "Resume Printer" in CUPS. I'll try that too.

I'm wondering, to print locally on Linux, I have to add the user to group lp. How is that working for a shared printer? Surely the Windows 7 user is not in group lp.

Here's an interesting bit:
I do have the 1102w driver set in both the Linux host and the Windows 7 client. Perhaps I need to figure out a way to change that ...

Easy enough to re-enable the printer via the CUPS web interface or using the 'cupsenable' command, but it will only help if the printer is disabled or stopped for some reason, and you can check the printer status from a terminal using
That only applies to local printers connected to USB ports. Its not relevant for network-attached or CUPS printers. (Most modern distros are managing CUPS USB-connected devices with ACLs these days anyway.)

Ok, FIXED!, again. This time it had to do with "a print job being sent through a filter twice, once on the local machine and once on the remote." I had the 1102w set up with the foo2zjs 1102w on the Linux host, and with the HP 1102w driver on the Windows 7 VM. It kind of makes sense that if the print job is formatted for the 1102w on the client that it would confuse things to run it through the driver again with CUPS. This particular issue would not be limited to the 1102w. Not sure why it worked last week with the PCL5 driver on Windows ...

So, what I did was create 2 queues in CUPS; one with the foo2zjs driver for local use (not shared), name: HP_1102w, and one with the "raw" driver, shared, name WIN7_1102w. On Windows, I added the WIN7_1102w printer per my post #35.

I would have rather been able to set a raw driver on Windows and therefore only have 1 queue in CUPS, but there is no raw driver in Windows and "Generic" only produces text output.

It seems like this would be a common issue with printers shared from CUPS to Windows, but apparently hardly anyone does this.

let's hope this problem stays dead this time!

1 members found this post helpful.

Double filtering! Yes, I nearly suggested checking that. Thanks for the update.

And thank your for all your help and patience. I could not have solved this without the link you gave for the Smart Install disabling software. Too bad HP's own link, supposedly to this software, goes nowhere useful. I did post that information, and the correct link on HPs website.