0

Issue
We have HP2035 on our network that for no apparent reason, on its own accord will print this gibberish:

Picture 1
Picture 2

Additional Background
Now, it'll print other documents just fine, it's just between the print jobs it'll print those gibberish pages. The print queue is complete empty, when that happens.

Setup
It is running on print server Windows 2008 R2. It is a PCL driver and up-to-date.

What was done
I restarted the print spooler as well as the server (stop and start, emptying the %windir%\System32\spool\PRINTERS). Checked for to make sure the driver is up-to-date. I checked the settings on the printer as well and nothing jumped out.

Help!
So, please, help! I have seen someone suggesting installing PS driver instead or uninstalling and reinstalling drivers, I really would do as a total last ditch effort as it's a remote site and I might have to deal it individual drivers as well, it'll be a big pain, but I will do it if I have to. Thank you!

Improve this question
0

2 Answers 2

Reset to default
2

The gibberish print job could actually be spooled from another PC with the wrong drivers. When a print job is created, the local drivers generate the data to be sent to the spooler on the print server, and not the drivers installed on the print server.

You'll have to see what clients are pointing to this print server, which might be challenging. But you do have a hint -- the client has the PCL driver.

Improve this answer
1
  • It might be problematic as it's also a DC...
    – George
    Commented Oct 29, 2015 at 16:05
1

As far as I can see (here and here), the 2035 supports PCL5E. PCL-XL (i.e. PCL6) does not seem to be supported - which is why you are getting that garbage. However, when I look for the drivers here, only a GDI driver is available - and none at all for Server 2008.

Someone has a PCL6 driver installed, and you'll need to replace it with the correct driver. If the printer is networked, the PCs can print direct to it, bypassing the server.

Improve this answer
1
  • That second paragraph--I was thinking that too. Looks like someone's printing directly, not to the queue. There might be multiple people/PCs bypassing the queue, and it would be one of those that's the offending machine.
    – Mathieu K.
    Commented Mar 20, 2016 at 7:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .