7 replies
by svc
My office has a similar setup with an NT network and I use HP Jet Admin for two reasons.
1. It helps to take some of the load off of the server for handling the print request.
2. It allows the printer to be setup as a device hanging off of the network with it's own IP address instead of being hard wired to a system.
by aspiring_one
by sgotero
by aspiring_one
by bmccool
Okay here's my 2 cents.
Assuming the HP printers are going to be attached using the JetDirect card anyway.
(Disable the protocols you don't need on all the jetdirect cards)
there are then 2 ways to connect everyone to these printers.
1) FREE FORALL, each machine is configured for each printers IP/IPX-SPX - MAC address, and printer drivers are installed.
Pros: Fast printing, simple in concept (like a party line)
Cons:Increased network traffic (each pc polls each printer's status), may cause slower logons as each printer is queried.
2. Server Queues, jet direct ports defined on one or more servers, drivers loaded there.
Pros: Queue control, a failed printer can be paused and it's queue redirected to a functional printer. Clients can attach new printers from a browse window.
Con:increased server load, need for disk space for the temp spool files.
Personally I like option 2, but it's your call.
by aspiring_one
by aspiring_one
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending