NT 4.0 Print Server Spooling issues

[crazyadmin]

I have trouble with the Spooler on and NT 4.0 print server locking up when any printers have errors. For example there may be a job for HP8000 pending, but the printer is out of paper, if a user sends a job to HP4000 it will not print until the HP8000 job clears. I have not found anything on Microsoft pertaining to this. I am using mostly HP laserjet printers, on my server I have service packs 3, 5, and 6a all loaded in that order. Anyone had similar problems/remedies??

 

[yizhar]

HI!

The following info will help:

* What drivers are used for each printer?
* Are the printer set up as local or network printer at the server (local is the correct setup)?
* How does the server communicate (Port) with each printer - LPT,LOCAL UNC PORT, LANMAN PORT, GENERIC TCP/IP, JETADMIN?

Bye
Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[crazyadmin]

The printers are set up as local and printing via LPR. Almost all printers have a Jet direct card and I will print to say 172.16.102.10:RAW. I am using Post Script, PCL 5e, and PCL6 drivers. I have downloaded the most current drivers from HP and I have also updated all of the firmware for the Jet Direct cards. A majority of the problem printers have PCL5e drivers, but those are the only ones that can be used due to formatting issues with PCL6 and PS.

Kai

 

[crazyadmin]

Has anyone else experienced these problems?

 

[zoeythecat]

Hi,

I would like to help but need more information.

* How are your printers shared?
* How are your ports created? You don't have the HP8000 sharing the same port with the HP4000?
* Analyze your printer properties for each and list how the ports are setup, and what drivers you have for each.
* Are your printers on 1 server or are they on several servers? You mentioned about some servers having Service Pack 3, 5 and 6A. There may be spooler issues with older service packs. May be good idea to upgrade your servers to 6A (Unless you have applications that will not work with newer service packs. Check on this before upgrading to latest service pack because you can't roll back without reinstalling NT)

Bob

 

[crazyadmin]

I have two print servers, they both have SP6a currently, but they have had SP3 and SP5 installed prior to 6a. Both the HP8000 and HP4000 are on the same server but I have similar problems on the the other server. I have about 20 printers on each server, but there never seems to be more than a few jobs going at a time and the server does not seem to be stressed. I have added the printers as local printers using an LPR port, I then have them shared as HP4000, HP8000, etc. They each have their own IP address therefore they are each on their own port. All the drivers are ones that I have downloaded from HP for that exact model and they are the basic drivers (not the whole package drivers that come with the stupid diag programs that load up). I am not sure if it has anything to do with the fact that there were prior service packs on the system. Everything looks to be set up right. I have had this problem for it seems like forever.

Thanks,
Kai

 

[zoeythecat]

It may be an issue with the LPR ports. Try creating a different port for the printer in question. Try creating a Standard TCP Port or a HP Standard TCP/IP Port. I've had some weird issues with LPR ports. The LPR Ports work well for older HP Printers. For the newer printers like the HP4550, HP8000, I have used either Standard TCP/IP Ports or HP TCP/IP Ports. Try this and see if it helps.

Contact HP if the above does not work. I'm confident that it is related to possible known issues with the LPR port that HP knows about. I have had Technical support calls to them with issues (Sorry, not sure if the issue is similar as yours as it was a long time ago) and they recommended changing the port from an LPR port because of known issues.

Let me know how you make out.

Bob

 

[Maruis]

Hi

Safe yourself some time and trouble and go straight for IP printing. Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[zoeythecat]

Marius,

He is doing IP printing. Can you explain what you may be talking about? The way you print over an NT network is by setting up Printing Ports (I.E - LPR, TCP/IP) and you configure the IP Address and share name to allow cliens to print.

I'm a little confused on what you mean by straight IP Printing? You need to be a little more clear than that.

 

[Maruis]

Hi

Let me be more clear......

Have seen HP printers that has problems printing via PCL.

If you have set up your port via IP and it keeps on disconnecting or loose your printer, the problem lies with your driver and how NT communicates with the printer.

It has been a while since I last worked with it so bear with me, is a bit rusty.

As far as I can remember you have to check if your printer cable is bi-directional or not...most aint. If connected localy.

Secondly go RAW or Post Script.

You have to play with your printer settings to get it working and keep it working.

Also try stopping and starting your spool service in NT.

When your printers are networked they are not local printers. Local being connected to your LPT1/2 port.

Another point is to make sure that the IP/IP's you use are not part of your DHCP range. Make them static and exclude them from your DHCP range.


Another thing that was mentioned...

No need to load NT service packs in order. You only need to load 6a, it contains all the the previous services packs. Also remeber the roll-up service pack after 6a.

Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[zoeythecat]

Marius,

Very good advice. Thanks for clearing that up.

He also should try and change the Port if your suggestions don't work. Again, I have had issues with newer HP printers where HP has had me change the port because of issues with LPR ports.

 

[conceptumator]

I'm no expert on NT, but what I did that was eaisest with HP JetDirect Printer Servers was to go to the server and turn on the protocol for Microsoft DLC. This let the server see the JetDirect port on the network without any LPR settings.

 

[zoeythecat]

Conceptumator,

Yeah, there are so many ways to setup a printer on a network. I guess it will depend on the type of network you have. Like noted, if your network uses DHCP, you want to make sure you have a static range excluded for things like printers, etc. Then you configure the IP Address on the printer. Once the IP Address is configured you plug the network cable for the printer in and power up the printer and boom your printer is on the network. You then have to login to your NT Server and setup the printer. You basically add the printer and during the printer install you are prompted with a screen to enter the IP Address and create a port you would like. By default a LPR port is setup. Now, if you install the Jetdirect software on the server this will give you another option. You can select a Jetdirect Port.

I think "crazyadmin" would have to define what type of network he has and how his printers are setup and how his ports are defined. But I am guessing that he is using LPR ports.

 

[Maruis]

Hi

I was reading the post again and something else came to mind....

It is not only the server side one has to configure but also the client side i.e. the ws.

You have to make sure that the ws has the correct driver and set to use pcl, raw, ps or whatever there is avialable or applicable in the set-up.

Many a time the server side is configured 100% and all the time the problem is on the ws end.

It can also be that the ws lost connection with the DC and then he also loose connection with the services i.e. printers. This will point to a network problem and not a printer/server config problem.
Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[ejstrom]

This is more than easily solved go to the following thread

thread55-212435

This is the only way I found that will work, I use this on all my client's networks

 

[crazyadmin]

Thanks all for the help, I checked and I had already done pretty much all that was mentioned except disabling Bi-Directional communication. The server has been running great for like two weeks so I have been very hesitant to change anything, but what the heck. I just removed Bi-Directional communication from all the printers. Time to see how she runs.

 

[Mithrindal]

We originally had a lot of probs with HP printers connected to the Terminal Server, maybe of some relevance, maybe not. The problem turned out to be the drivers HP supply with new printers. Even the high end printers come with drivers for a single user which caused ULA errors on our NT Terminal Server. The solution was to download the corporate version of the printer drivers from HP's web site.

Hope this helps.

Cheers

PH.

 

[Guest_imported]

Hi,
i want to exported printed documents from print spooler to excell formate is the any method or utility for this.

thanks
kiran