Discussion Locked

hp 4000n pausing between print jobs

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a laserjet HP4000n on a network. The workstations are on win2000 and the print server has just been recently upgraded from NT to win2000. We changed the print driver to a pcl 6 win2000 driver from a pcl NT driver. The printer now pauses between all the jobs and takes 10 times longer to print? Any ideas?

18 replies

by carlos.nino

Did you completely eliminate all related items (printer drivers, shared printer resources...) and install it from scratch.

by shawn

I am assuming that you didn't change the name of either the server or printer during the upgrade, and this is how your users connect to the printer (via \\server\printer). You may need to (begrudgingly) remove and re-install the printer from the client workstations - they may still be using the PCL-5 (NT) driver (from before the upgrade), instead of the PCL-6 driver. I have had this same issue with more than just HP printers, and most of the time deleting and recreating the printer on the workstation fixed it.

by dbrown

We upgraded the print server (a couple months ago)while it was in NT. We recently upgraded the server to w2k server. I have had the user deinstall and reinstall the printers with no luck.

by rcom

The "N" at the end of the printer's name stands for network so why is it connected through a Server? Are you using a parallel cable? It should be connected directly through the LAN using the built in nic.
Other than tracking printer useage I don't see why your not using this feature. The oldtime print server is no longer needed.

If the printer's IP settings match the rest of the LAN it will show up like a workstation. You may need to allow it through the firewall.

The LAN settings can be modified through the printers buttons. Or you can use HP newer version of Jet Direct software. If you're using DHCP change to that or give it an IP address and set up the gateway and DNS.

This will be way faster.

After setting it up go to the N-hood on the workstations, right click on the printers icon and select install. This quick and easy task can be performed by your users.

by dbrown

At this point, we are using a print server. At this point, all the other printers seem to be working. Thank you for your suggestion but we prefer to fix this problem and at a later date look at IP printing.

by nospam

What kind of hardware for the print server? Win2000 needs more CPU and RAM then the old NT. What version of the PCL6 are you using? 4.3.2.201 on HP site.

by dbrown

The server is HP ML360 with 1.5gb memory. The version of PCL 6 is 4.4.2.201.

by tyrone

All of the users are still going to be using old drivers, assuming of course they are all on 2K machines. Upgrade 1 client to test and try again. It might be worth renaming the print server and writing a script to auto update the clents when they log on.

by dbrown

I have had the users deinstall and reinstall the printer and I installed the driver on the w2k pc. We have about 10 users using this printer so it probably won't do it through the login script.

by dbrown

In answer 4, their is a typo in my reply ....the pcl version is the same as in the answer. 4.3.2.201 on HP site.

by dbrown

We now have users complaining about our HP 9000 also taking alot longer to print multiple jobs. It also seems to pause.

by rcom

There's no issue with the drivers. The drivers are ready to install from the Server.
On the Server open the printer Properties.
On the Sharing tab, click Additional Drivers.
Choose the operating systems of the client computers. Users on client computers can connect to the print server and automatically download the same drivers.
From the workstations go to the network n-hood and find the shared printer. Right click and select install.

Are you using the LPT ports or the LAN to the server. I'll assume since you have more than one printer that you have something like a jet direct box or the printers are connected directly to the switch/hub.

Windows 2000 will automatically configure the printer to use SMP (Standard Port Monitor) instead of LPR. This uses SNMP (port 9100) then picks a random port somewhere about 1030 to communicate. This may be causing a problem if the an LPR driver is running on the Server or if the firewall is constantly checking each time a packet comes across. To test disable the firewall and see if there's a difference.

If it is a jet direct box then I'd suggest getting the latest firmware.

If you don't have more than one of the same types of printers attached to the Server disable printer pooling.

by dbrown

The question wasn't fully answered, BUT you lead me in the right direction! Thank you!!! We change the port type to TCP/IP and it took care of it! We are changing all of the printers on our print server.

This discussion is closed to new replies.