5 replies
by dmatlock
by qb4006
I figured it out myself. The firmware on the printers Jetdirect network card had to be updated.
Thanks anyway
by ann777
How often do you reboot the print server?
Generally most of the NT printer prolems can be resolved by stopping and restarting the Spooler service. In fact, MS recommends that people try restarting printer services in this manner when jobs getstuck in the queue.
But, to have it happen once or twice a day (with the same printer), is too often and probably points to something server-side that is probably getting tangled with resources. I'd reboot the server (if it has not been done within the last week), and see if the problem goes away for awhile.
If the server has been rebooted recently, then check the memory in the printer, check the network cabling to the printer, and make sure it's all tight and secure (and that the cable is not being jolted out of the connector, or that a vacuum hasn't eaten part of it, etc.).
Reload the drivers on the server if the problem persists. And check the nic in the printer for link lights and proper configuration.
by qb4006
I figured it out myself. The firmware on the printers Jetdirect network card had to be updated.
Thanks anyway
by qb4006
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending