Print Server w/ Windows 2003 Server

[PloKoon]

i'm setting up a small network for a business, and coming across an issue that i haven't really had experience yet with.
this particular network has about 8-10 computers, most of which run WinXP.
i installed Win2k3 Server on the server box.

most workstations have their own laserjet but there's another printer (HP DesignJet 500) that is directly plugged into the network switch.

now, i've set up a print server role on Win2k3, but on all the other machines i had to go into 'add printer' and either add the DesignJet by 'network printer' or under 'local' you have the option to change the port to 'HP Standard TCP/IP'.

either way, it doesn't seem like it's setup correctly, what we are trying to accomplish is when a workstation prints some plans (very large plans for the DesignJet), it really bogs the workstations down, and i was under the impression that a print server is supposed to lighten that load, even transferring the load to the server itself.
is this true?

i think my problem is i have the DesignJet setup as a 'network printer' on all the workstations as opposed to actually using the print server functionality that i would like to w/ Win2k3.

any help would be greatly appreciated!

should i setup the Win2k3 box as a dhcp server? use Active Directory?

 

[taxi]

With the way HP DesignJet drivers work, you are almost always better to have the workstations print directly to the plotter. Though I have never used a 2k3 server with a DesignJet. You should try checking the DesighJet forums on HP's site.

Also try playing with the spooler settings.

As long as all you TCP/IP communication is running correctly, DHCP will not help. AD will not help at all.

The print server is an internal HP JetDirect card?

 

[PloKoon]

you mention a jetdirect card, i don't have such an item, but i've seen people talking about it on HPs website.
would i still need a jetdirect card even if i have a 'print server role' setup on win2k3? i thought that the OS could act as a print server as opposed to having to get a jetdirect card...

also i see that switch boxes are incompatable w/ DS products, even though it has been working, just random lockups and lag on the workstations that are plugged into the same switchbox.

should i have the DS500 plugged into the Win2k3 machine instead of the switch?

 

[JackMDS]

Using the jet irect makes the printer an Ethernet device independent from a specific computer (it plugs to a regular switch).

Connecting the printer via the regular port to the computer with Win2003 allows other computers to share the printer as long as the Win2003 machine is on.

You have to install the drivers of the printer on all computers, switch On the share on Win2003. The printer will appear as a Network printer on other computers.

 

[blcjr]

i think my problem is i have the DesignJet setup as a 'network printer' on all the workstations as opposed to actually using the print server functionality that i would like to w/ Win2k3.

If you've installed the printer as local on the Win2k3 machine as a standard TCP/IP port, and have shared it, then you are "actually using the print server functionality" of Win2k3, i.e. it is the print server. Then setting the resulting printer up as a 'network printer' on the workstations is not only not a "problem," that's the way you are supposed to do it.

Can you be more specific about what is happening on the workstations when they print? If configured correctly, the only possible "bottlenecks" are (a) the network, and (b) the print server. As far as the print server is concerned, available RAM, CPU type and speed, HD type and speed, and amount of free disk space are all possible factors in performance. We're not trying to print from multiple workstations at the same time, are we?