JetDirect Pinter server - best practice
From: Alice (anonymous_at_discussions.microsoft.com)
Date: 05/03/04
- Next message: Alice: "memory could not be written"
- Previous message: cavatino: "RE: Error Print Job staying?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 3 May 2004 13:10:55 -0700
I agree with you to a point.
I have 2 print spoolers with about 30 printers installed
on each, primarily HP brand with a few Xeroxes thrown in.
My original configuration included the HP Jetdirect
software, but I began to have problems with it once I went
to W2k on the spoolers. I finally uninstalled the
Jetdirect software and installed all printers
using 'standard tcp/ip' ports. I have had no problems
since.
Alice
>-----Original Message-----
>Hi,
>
>What is the best practice for network printing? We are
>currently attaching our printers to HP JetDirect print
>servers. Assign an IP address then create a TCP port on
>the client pointing to the printer's IP. Is this the
>most effective way in setting up network printing?
>
>Thanks,
>John
>.
>
- Next message: Alice: "memory could not be written"
- Previous message: cavatino: "RE: Error Print Job staying?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
