I have a printer attached to a network. The printer SAYS that it has no documents COMING to it for printing. The printer queue on the network indicates that the queue is building up.

How do I get the printer to REALISE its mistake and start printing the backlog of documents?

I have tried stopping and STARTING the printer queue via the menus on the printer queue,but to no avail.

ThanksMake sure the RIGHT printer is selected.
If it is, restart the printer, and then the computer.

Also, what Operating System and what Printer is this?The printer is attached to a network running Windows Server 2003. There are a number of users all using a mixture of Windows 2000 Professional and Windows XP.

I've tried switching the printer off and on again (I even pulled out the power cable).

How can I restart the PC when there are a number of PCs sending documents to the PC? Do I have to restart the server to which the printer is attached?I would end all tasks, then restart the computer that the printer is set up on.1) Make sure the printer is not in "Offline" mode.

2) Check the IP port the print queue is using on the Windows Server 2003 box.  (i.e.: IP_10.0.0.20)

3) Check the IP address on the printer itself (i.e.: 10.0.0.20).

4) Make sure the IP addresses of the port in #2 and the TCP/IP settings on the printer in #3 are the same.  If they're not, nobody's printing.

5) If they are the same, then on the Server 2003 box: Start -> Run -> services.msc -> stop and start the Print Spooler service. 

6) If that doesn't work, reboot the server and the printer at the same time.

7) If that doesn't work, check the NIC on the printer.  It could be bad.  Alternatively, make sure the cable is not bad.  Also make sure the port on the switch the printer is going to is not bad.Thanks for all the great help on this one.

The problem has now been solved. The print server needed a kick up the rear end processor. In short, it needed rebooting.

I shall hold on to all of your tips and refer to them in the future.

Thanks again.