11 replies
by opatzg9
by bfeltus
by mike jones
Have you set the job to print directly to the printer?
This could be where the problem lies. You need to allow the job to spool properly on the Novell Server which will then talk to the jetdirect card properly and not send too much information at one time.
By bypassing the server, you are sending to much information to the printer which can't recover itself.
I suspose you could add more memory, but I would check the way that the job is being sent.
by bfeltus
by an_it_guy
Theres something called as 'Priority' which can be set from 1 to 99 (default being 1). Check the printer properties from both the user machines, and make sure they have the same priority, so that UserB's jobs dont keep UserA's print Jobs from printing.
Best of luck.
by bfeltus
by ssuckle
by bfeltus
by budthegrey
A couple of options:
Lengthen the timeout in the capture command (the TI= paramter), especially if this is a search & print style report. you may need a value of 15 or more.
If there is a server that is local to UserA, create a queue on that server and program the jetDirect to service it as well as the remote queue.
by bfeltus
by bfeltus
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending