Windows Forum

Ask something
Discussion Locked

Network Printing Problem

0 helpful
8 replies

by guy 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I arrived back at work on Friday to find that all network printing on our admin domain had failed. (No work had been carried out on the server, or software installed) The job was hitting the spooler but sticking at 4 KB then stopping there. We are on NT4 (sp6) servers with 95/98/NT clients, running jet admin on the server & HP LaserJet 4000n / Epson dot matrix printer. The dot matrix would still print using jet admin but not the LJ4000. (Stopped printing with jet admin as well today) The LJ4000also decided to use an already allocated IP address for itself (greedy).

Then tried using the DLC protocol for LJ, this has worked on one server but not the other. We've tried the usual stop/start the spooler, clearing the spool directory and deleting and re-installing the printers but no luck.

Any suggestions as to what to try next?

8 replies

by dft3

I strongly suggest you get off of service pack 6 because it is full of bugs. Service Pack 5 is the most stable to date. A lot of vendors don't support 6 yet because of this.

This isn't the first problem I've heard about with SP6 and HP Jet Admin. Give it a try. It will probably fix your problem.

Good Luck!

by guy

By late last night we sorted the problem.
We removed the jet admin ports and re-installed the printers using dlc and
hey presto.
So jet admin really had screwed up.

by kevin brown

Try this. stop the spooler and delete both the printer port and the printer. Restart the spooler and then reinstall both the printer and the jet direct port.

by guy

By late last night we sorted the problem.
We removed the jet admin ports and re-installed the printers using dlc and
hey presto.
So jet admin really had screwed up.

by mwong

Check the timeout settings on the individual printers. If they are set too low and there is network contention, it is possible that the printers are timing out before receiving all of the data. Try setting the timeout to Zero which will cause the printer to wait indefinitely for a print job to complete. Good luck.

by guy

By late last night we sorted the problem.
We removed the jet admin ports and re-installed the printers using dlc and
hey presto.
So jet admin really had screwed up.

by re_hughes

Never use DHCP to obtain an adress for your print server. set the server back to factory default and issue it a IP address outside the DHCP scope. Then reassign the printer to that port.

by guy

By late last night we sorted the problem.
We removed the jet admin ports and re-installed the printers using dlc and
hey presto.
So jet admin really had screwed up.

This discussion is closed to new replies.