Slow printing with Windows 2003 print server compared to NT4 printserver.

I have recently upgraded my servers and network software.
I have gone from NT4 to Windows 2003 on all my primary servers.

I have installed all printers on my new Domaincontroler.

But now Iam experienceing slow printing to one of my printers.
I have still the old NT4 box running with the printer shared aswell, and if I print via that server everything works just fine.
(Iam printing big CAD drawings and projects to the printer which is a HP Laserjet 5.)
I have tested with a HP6p printer and it seems to have the same issue.... fast print on NT4 but slow print via 2003.

All settings on each server are the excact same for the printers.

Any ideas why its slower via Windows 2003?

If you need more information please post your questions.

Thanks in advance.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Tim HolmanConnect With a Mentor Commented:
What sort of HP printserver ?  You mean the appliance ?

So you're saying that the printer is connected to an HP printserver, but printing from an NT server is faster than printing from a W2K server ?

Whatabout if you print from your clients, rather than servers ?  Or are your printers shared on the servers, but redirected via IP printing to the print server ?

If you could explain the flow of print jobs in both scenarios this would help.
Have you tried bumpping up the printing priority?  Try setting it to 99 for kicks and see if that improves any.

- Info
You need more memory and faster processor to get the same speed in w2k3 which is also domain controller.
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

GrodelAuthor Commented:
Yeah Ive tried that.
No difference in printing speed :(
GrodelAuthor Commented:
The old Box:
P2 350Mhz with 1gb RAM

New Box:
P4 XEON 3.0GHZ with 2GB RAM

And all its running is DC and Print.

I have file, mail and apps on their own servers.

If thats not enough I have a problem :)
Tim HolmanCommented:
Could be SMB signing ?  If you use XP clients, then look at this:

I think the hardware configuration is ok. You can now verify if the spooling or the printing process is slower. Choose a one page project and print it. Try to monitor the printer on the server, where you can see the spooling and the printing process. If the printing is slow, you may need to reconfigure the printer port. If the spooling is slow, it's a network or harddisk problem. I've seen this when I've replaced and old server with scsi disks with a new one with ide mirror.
GrodelAuthor Commented:
Ok... Ive checked SMB signing and it dosnt seem to be the problem.

There is no network or hardware slowdown.
The network is the same if I use the old server or the new server. (They run at the same time and when using the old server the prints fly out but when using the new server the printer prints a page and the says processing job)
I did check the "Print after each page" setting and it dosnt make a difference.
The new server is 10 times faster than the old server.

Any more suggestions?
Anything I can try please :)

There are another settings to compare on the two print servers: Bidirectional printing, print directly to the port and the print processor.
Tim HolmanCommented:
To reiterate - are you saying that the printer is directly connected to the NT server via parallel cable, and printing works fast, but when you put that cable into a W2003 server, things are about 10 times as slow ?
In this case, I would suspect drivers.
GrodelAuthor Commented:
No.. the printer is on a HP printserver.
So its a network printer.
crissandConnect With a Mentor Commented:
I guess it's a jetdirect printer, installed on the w2k3 DC as shared printer published thru Active Directory? Well, what type of tcp/ip port have you created, HP or Standard? As far as I know standard tcp/ip port is faster than the hp jetdirect port. Very important is the acces time to the disk where the spool is located, If the wnt server has scsi controller and the w2k3 server has ide or sata, this can be a reason of different spedd (I've seen that). Or the nt has 1 disk and the w2k3 has a matrix raid.

There are two phases of printing, and you must monitor them to see if the spooling or the printing is slower. Sometimes bad network cables or switch/hub ports can give delays.
GrodelAuthor Commented:
I never really found the answer to this.. I suspect it to be some sort of driver/port problem.
I have other printers installed on the server that works just fine.

The solution was to buy a new faster printer.... so now everyone is happy except our financial manager :)

I have split the points between 2 of you since you both came up with good answers :)

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.