General discussion

Locked

We recently moved all our print queues f

By cap_170 ·
We added the printers as local printers on the NT server using HP JetDirect ports pointing to the remote printers via IP address. 2-3 times a day jobs get stuck in printing queues and we are forced to stop and restart the Spooling service on the server to resolve the problem. I have had this problem with other NT print servers in the past, but thought this was a limitation in NT Server 4.0.
I cannot find any information pertaining to this problem on Microsoft's TechNet

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

We recently moved all our print queues f

by JimBb In reply to We recently moved all our ...

Try changing the print data format for the ports. You want your printservers to handle the "RAW" data, and let all of the formatting etc. be done by the client's printerdriver. We had the same problem (on NT4), and though not all problems were over, it reduced the restarting of the spooler by about 90% for us, for a printserver with some 200 printers.

Jim

Collapse -

We recently moved all our print queues f

by cap_170 In reply to We recently moved all our ...

The question was auto-closed by TechRepublic

Collapse -

We recently moved all our print queues f

by RCC In reply to We recently moved all our ...

My advice is to uninstall and reinstall the printing services and ALSO reapply the latest NT service pack. We had similar problems and by upgrading all the firmware in the JetDirect printservers and doing the above we've got read of the problem in our configuration (multiple NT domain, multiple server, printing TCP/IP over LAN and WAN connections).
Regards,
Radu

Collapse -

We recently moved all our print queues f

by cap_170 In reply to We recently moved all our ...

The question was auto-closed by TechRepublic

Collapse -

We recently moved all our print queues f

by techrep In reply to We recently moved all our ...

Check your IP addresses, make sure you don't have some static addresses on workstations or the JetDirect cards confilicting with dynamic addresses from a DHCP server. One machine that is using a static address but is turned off while others are getting dynamic addresses from a DHCP can cause a problem if it happens to have the address of a JetDirect card and then gets turned on.

Collapse -

We recently moved all our print queues f

by cap_170 In reply to We recently moved all our ...

The question was auto-closed by TechRepublic

Collapse -

We recently moved all our print queues f

by cap_170 In reply to We recently moved all our ...

This question was auto closed due to inactivity

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums