HP LJ 1020 Spooler Service Restart Revisited

My previous fix for the HP LaserJet 1020 Spooler Service Restart issue did not stick. Upon reboot of the server, the problem returned and was not correctable in the manner previously described.

I researched the issue again and found a Microsoft forum post where they actually fixed the issue. The fix goes as follows:

  • NOTE: Do this on the machine connected to the printer.
  • Run gpdedit.msc
  • Go to “Local Computer Policies\Administrative Templates\Printers”
    • Set the setting “Allow print spooler to accept client connections” to “Enabled”
  • Go to “User Configuration\Administrative Templates\Control Panel\Printers\”
    • Set the setting “Point and Print Restrictions” to “Disabled”
  • Close the Group Policy Editor
  • Go into the Printers and Faxes control panel, right click on the printer and hit properties.
  • Click the “Ports” tab
  • Uncheck “Enable Bidirectional Printing”
  • Close the Printer panels/windows
  • Run a command line, type in “gpupdate /force”, and hit enter

Fixed!

The forum fix was here.

HP LaserJet 1020 Spooler Service Restart

UPDATE: The following procedure did not work for very long. See the new procedure.

If you are sharing an HP LaserJet 1020 USB printer over a network, and you have problems printing to it without restarting the print spooler service on the “server” machine (like people here, here and here are having), I found a solution that works for me. Maybe it will work for you too.

Quick Fix

Put the user who is printing to said printer over the network into the “Print Operators” group. If that doesn’t work (or you aren’t on an Active Directory domain – i.e. most users), try setting the security on the printer so that “Everyone” has “Print”, “Manage Printers”, and “Manage Documents” allowed. (Open up Printers/Faxes, Right click the printer, hit properties, hit the Security tab, select “Everyone”, put checkmarks in all the “Allow” boxes, hit OK.)

It may not be the most secure policy, but it sure beats buying another printer and then waiting around for the printer to get there. I find it makes a good “crutch” solution in a pinch.

Reason

The print driver on the 1020 is HOST based, not PCL based. The problem I was having was that anyone who was not an Administrator would trigger the issue. I surmise that the HOST based driver requires a certain level of permissions from the user in order to fire off the job properly. Weird, but now solved.

My first professional printer repair

I did my first professional printer repair today.

The short story: laser printer repair is remarkably easy.

The long story: Had an HP LJ1200 at front desk and a LJ1000 in the shop. The 1200′s laser unit died a few weeks ago (according to the local, and very cool, printer shop). We replaced it and kept it around for spare parts. Then, a few days later the 1000 has an electronics problem. Here’s the cool thing: the 1200 and 1000 physical innards are almost identical. The mainboard and formatter board are not, however. (again, thanks printer shop guy!)

So, I called the printer shop guy and asked if the laser unit could be removed from the 1000 and put in the 1200 giving me a new printer. He said YES, and gave me a quick rundown of how to disassemble the units.

I tore down the printers and swapped the laser unit. BLING! Now, we have a working printer for the shop again.

I really should look into doing printer repair for the business. Could be a good thing. Don’t want to hurt the local printer guy though, he’s really cool.

Fix missing services & Active Directory / Remote Desktop / Network Printer Missing

It’s a two-fer today.

First off,  if you have a Windows XP machine (2k variants, too probably) that has a completely missing, yet normally present system service, lets say like, Windows Audio, you can fix it fairly easily by "grafting" it back in from another computer.

  • Find another computer with the same version of XP/2k/2k3/Vista
  • On that computer, Run regedit
  • go to HKLM/System/CurrentControlSet/Services
  • Find the system service on the good one that is missing on the broken one
  • Right click it’s key and extract it somewheres
  • Take the resulting .reg file to the broken machine and import it
  • Reboot the broken machine
  • Fixed!!

And now, part 2! This is a weird thing, and I will try to explain it in a way that helps people find this online in the future. If:

  • You have an Active Directory Domain
  • A Terminal Services server users log into (or a Domain Controller using the 2 remote administration consoles)
  • Users at a physically different location
  • A printer mapped on the Terminal Services server OVER THE LOCAL NETWORK
  • This mapped printer is physically attached to another computer in the same network as the Terminal Services machine
  • AND for some reason Terminal Services users cannot even SEE the printer when logged in via RDP/Remote Desktop

This occurs, usually, because the computer to which the printer is attached does not give Domain Users rights to print to it. Yeah, I know, I thought the server would override local workstation security, but it apparently does not.

  • Go physically to the computer where the printer is connected
  • Go into the printer properties
  • Hit the Security Tab
  • Add Domain Users and give them "Print" control.
  • Apply, OK
  • Fixed.