<div>
Check if you have the latest drivers installed for that printers.
</div>


Check if you have the latest drivers installed for that printers.

<div>
It seems that disabling bidirectional printing fixed the problem. Now my only question is, why?
</div>


It seems that disabling bidirectional printing fixed the problem. Now my only question is, why?

<div>
It happened to me some times.<br />
<br />
If the printer is bidirectional, the language monitor allows you to monitor printer status. You can request configuration and status from the printer, and the printer sends unsolicited status (such as “Paper tray empty”) to the client.<br />
<br />
Any bidirectional print device that uses a bidirectional port monitor that uses PJL can use the PJL language monitor.<br />
<br />

</div>


It happened to me some times.

If the printer is bidirectional, the language monitor allows you to monitor printer status. You can request configuration and status from the printer, and the printer sends unsolicited status (such as “Paper tray empty”) to the client.

Any bidirectional print device that uses a bidirectional port monitor that uses PJL can use the PJL language monitor.



<div>
So why would enabling enabling bidirectional printing cause the jobs to get stuck in the queue?
</div>


So why would enabling enabling bidirectional printing cause the jobs to get stuck in the queue?

<div>
<div class="content wysiwyg-content">
I recently moved printers from our old print server 2003 to our new print Server 2008. All printers were added to the new server via standard tcp/ip port.<br />
<br />
The problem I have is that everytime a user prints to one of these printers on the new server, the jobs just sit in the queue. If I restart the print spooler, all the jobs print out, but then new jobs just end up sitting in the queue again.<br />
<br />
What is the problem? As far as I can tell, all permissions are set correctly. Help!
</div>
</div>


I recently moved printers from our old print server 2003 to our new print Server 2008. All printers were added to the new server via standard tcp/ip port.

The problem I have is that everytime a user prints to one of these printers on the new server, the jobs just sit in the queue. If I restart the print spooler, all the jobs print out, but then new jobs just end up sitting in the queue again.

What is the problem? As far as I can tell, all permissions are set correctly. Help!

All print jobs stuck in queue on Server 2008

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

A printer is a peripheral which makes a persistent human readable representation of graphics or text on paper or similar physical media. Traditional printers are being used more for special purposes, like printing photographs or artwork, and are no longer a must-have peripheral; 3D printing has become an area of intense interest, allowing the creation of physical objects. An image scanner is a device that optically scans images, printed text, handwriting, or an object, and converts it to a digital image. Hand-held scanners, where the device is moved by hand, have evolved from text scanning "wands" to 3D scanners used for industrial design, reverse engineering, test and measurement, orthotics, gaming and other applications.

Printers and Scanners

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.