If you’re having problems with Windows Vista and a print server

Just wanted to help everyone out on the internets – this is a problem that at least a few people have come across (http://h30434.www3.hp.com/psg/board/message?board.id=Networking&thread.id=1020). It’s concerning using a networked print server with Microsoft Vista.

In my experience, the printer will either print garbage over and over, print nothing over and over, or print the first page over and over.  Either way, you’re wasting a lot of paper and toner, and it’s frustrating!

(Stop reading now if it’s not important to you :-P)

My specific setup may differ from yours, but this solved my problem, and it seemed to solve many others’.  I have an HP Color LaserJet CP1215 connected to a D-Link DPR-1260, and the computer trying to print is a Windows Vista machine.  The LaserJet and the print server are excellent pieces of equipment, definitely – just that they weren’t working together.

It appears that using Vista causes problems due to both:

  1. Microsoft not complying with the Line printing RFC, by allowing a computer to NOT send the size of the data that it needs to the printer.
  2. Print servers also not complying with the RFC, by accepting the computer’s print request even though it doesn’t have that magic size included.

So the solution that I eventually found is this:

Go to printer properties, and select Configure Port:

vista-printconf0

Change the port’s settings to LPR (instead of RAW) if it isn’t already:

vista-printconf

And then check LPR Byte Counting Enabled.

By doing this, you are telling the printer “Hey, I’m going to print a document of X bytes, so only print X bytes worth”.  This way, the printer knows when to stop printing.  My printer would just keep printing the job over and over and over…

Hope this helps any lurkers!  Please leave a comment if you’re helped out by this, or if it doesn’t work – I might have some other ideas.

~Chris

83 Comments

  1. camorris0001 says:

    just worked for me as well on a HP 2035n win WIN 7 64x. Thanks!

  2. SG says:

    This solved my problem too-(HP laserjet2035+TP Link TL-WPS510U wireless print server). Thanks a lot!

  3. Dom says:

    Great help! Thank you. It fixed my long ongoing problem with wasting paper and ink on Windows 7 64-bit laptop.

  4. Vic says:

    That fixed it – thanks!

  5. Harry says:

    It is work with my HP laserjet P2035 on window 7 64-bit through the hp printserver, thank you.

  6. placebo137 says:

    Great, worked for me too!!

  7. Vince says:

    Any idea if this fix will work on windows xp systems? If so I’ll get a D-Link DPR-1260 to go with the HP Color LaserJet CP1215.

  8. Timmby says:

    That fixed it for me as well for HP Laserjet P2035N Thank You!
    Win 7 64x P2035 print driver used as well

  9. Daniel says:

    Thanks!!!! It was driving me crazy. It fixed the problem.

  10. pacusan says:

    GRACIASSSSS!!!! te juro que estaba ya desesperado con esto, llevo desde las 9 de la mañana dandole vueltas… pero al fin me voy de finde con la satisfaccion de haberlo conseguido.

  11. Mike says:

    Simply unchecking the box “Enable bidirectional support” on the Ports tab of the printer properties worked for me.

  12. thed says:

    Great!!! Thanks! Win7 x64 + TP-Link TL-PS110U + CP1215 without “LPR Byte Counting Enabled” were going to infinite printing.

  13. oversteer says:

    Was having issues on a Win7-64bit laptop & networked P2035n printer. Fixed the problem! Many thanks.

  14. tremn says:

    I appears to have solved the problem fo me. thanks.

  15. azlan says:

    Was having issues on a Win7-32bit laptop & network P2035n printer. went printing infinite. after doing that, it fixed the problem! thank you very much..

  16. Will H. says:

    Thanks! It worked for me. I wish it came in the manual. Thanks for your help and for Sharing it on the Internet for the whole world to see. :-)

  17. Farzam says:

    Thank you, it worked for me too, on a network hp 2035n.

  18. rc says:

    I couldn’t do it the first way either as it asked for a queue name but disabling bidirectional support did the trick! Thanks!!

  19. Radwanullah says:

    Thanks this works for me

  20. Kacy says:

    Guy, you are simply the best.
    It worked for me

  21. Karen says:

    Thank you, it worked for me too, on a network hp 2035n.

  22. This solution worked for me.

    Thanks for providing solution

  23. Omid says:

    coooool. thx

  24. Kfb says:

    Thank you, worked perfect for me too. I have a hp cp1215 with dpr-1260 and Windows 7 and 8!

  25. Steve Banks says:

    Changing to LPR and “creating” a queue name, along with your LPR Byte Counting Enabled and it works like a champ on a Windows Multipoint 2012 box that has the printer set up in a remote office over an IPsec VPN tunnel. HP LaserJet P1606dn (to help with future searches).

    Thanks!
    Steve

  26. dougiemui says:

    thanks it worked for me…

  27. Sahar says:

    Thanks Steve, U kept my money 😀

  28. David says:

    Thank you! This works perfectly!

    #solved

  29. Terry says:

    Solution worked for me as well! Made me look like a hero! Thanks a lot!

  30. Tom63010 says:

    I have an HP laptop running Windows Vista. All my other PCs are Windows 7 and used to have Window XP machines. I have an HP CP1215 with a Linksys PSUS4 Print Server. The Vista based laptop was the only one having issues and it was printing a LOT of pages. This fixed the issue. The only thing I was unsure about is the queue name. I had to go to another source because my laptop rejected the name in the screen shot. I named it CP1215 and that worked.

  31. yajjie says:

    unchecking bi-directional printing worked like a charm for me. thanks guys

  32. Debbie says:

    Worked great. Had to create a queue name. Just made one up and it worked great. Thanks so much for your help. I have an HP1120W laser printer.

  33. Niti says:

    For some reason it didn’t let me change to LPR. By reading all your comments, simply unchecking the box “Enable bidirectional support” on the Ports tab of the printer properties worked for me. Thanks so much!!!

Leave a Reply