On our LAN I have one particular machine that seems to be clogging up the spooler/queue every time it prints to one particular printer.

Server 2008 Print Server; Win7 Box.

Every other machine can print to this printer fine. This machine can print to other shared printers fine.

What happens when it prints is the job is spooled and sent to the printer. The job prints. The job does not get deleted from the spooler--it just sits there saying "Sent to printer".

The only way to get this printer back is to manually go into the Server 2008 box and run

net stop spooler
del C:\Windows\System32\spool\PRINTERS\*
net start spooler

The error...err, "event viewer" is helpful as always (read: not helpful at all).

I've tried rebooting the machine and re-installing the printer--neither fixed the issue.

Any ideas on where I can look? What might be wrong?


  • 1
    Is it the machine or the user? Have you tried having the user login on another computer and print? Does it do it to a different user logged into that machine (a domain admin for example)? Do you have other win7 machines that print to that printer ok?
    – Omnikrys
    Nov 7 '12 at 13:59
  • It is the machine. Domain admin can not print correctly from the machine either. Other users (on other machines) can print correctly to the printer. Thanks.
    – stormdrain
    Nov 7 '12 at 14:06
  • Re-image machine. Beat user with LART for good measure. Nov 7 '12 at 14:38
  • @HopelessN00b or I could just change the port from WSD to TCP/IP and go out for a smoke. Yeah, think I'll do that :D
    – stormdrain
    Nov 7 '12 at 14:51

Found here: http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/6e72268f-4ec2-43a2-9a29-750204b02c3f

Changing the port from WDS to TCP/IP fixes the issue.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.