Re: Network printer
From: Roland Hall (nobody_at_nowhere)
Date: 03/05/04
- Next message: youssef sabri: "creating users"
- Previous message: jbatten: "FRS not starting"
- In reply to: Lanwench [MVP - Exchange]: "Re: Network printer"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Network printer"
- Reply: Lanwench [MVP - Exchange]: "Re: Network printer"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 5 Mar 2004 13:23:12 -0600
"Lanwench [MVP - Exchange]" wrote in message
news:ewY$YTsAEHA.3348@TK2MSFTNGP11.phx.gbl...
: Inline -
: > 1. The method Lanwench gave you. It is the easiest to install and
: > setup, even regarding user setup, especially if you're running NT and
: > above on the client because it can pull the printer driver from the
: > server. It is however, the worst scenario regarding performance.
: > There is no reason, IMHO, to add performance hits to your server to
: > print to a printer on the network. The upside to this scenario is
: > initially it will not cost you anything monetarily.
: My suggested method *presumes* that there is a JetDirect card or
comparable
: print server card in the printer itself - not directly connecting a
printer
: cable to a server.
Sorry, I just took it as is.
: The server merely shares the connection and handles the
: print spooling/processing.
Ok.
: If the network is large enough to warrant it, a
: separate print server should be used anyway.
A JetDirect is a separate print server.
: I don't want to set up TCP/IP
: printer ports on all workstations to print directly to the print server
Ok. You have options. I prefer to do it this way.
: - if I make any sort of IP changes, I don't want to visit a dozen
workstations.
Me either. That's why I use private networking so I never have to change IP
and should I ever have to for some unforseen reason, I'd script the changes
with WSH or use remote Administration.
: I also want the control I get over printing by having everything spool
: through a server
Are you saying you do not have control of a JetDirect card or an HP printing
appliance?
: - it's easy to delete hung print jobs, etc., and let
: clients manage them themselves if I give them rights.
You're saying that can only be done using a print share on a NOS?
: I can move users'
: printers from one print server to another easily using a batch file &
: con2prt and they never have to know about it.
I can do it with scripting or NetOp and accomplish the same thing. In fact,
I'm not limited to printing either.
I never said your method was wrong. I said it was the worst method for
performance, that's all. I do not see a need to add performance hits to a
NOS. You have now listed your reasons why you think it is ok. I use
different methods and I limit my performance hits on the server. I doubt
any way is better over another in the general sense. There are a lot of
variables involved. I listed what I thought the differences were and gave
my opinion. It's ok if we disagree. I'm not posting anything to change
your mind or modify your procedures. I'm just here offering my opinion, as
you are, and the OP should choose what works best for him. It may be your
way, my way or some other way but it shouldn't matter to us either way.
(O:=
Hopefully I have not offended you as it was not my intention to do so. I
gave my honest professional opinion, as I feel you do and always enjoy
reading your posts. If I have offended you, please accept my sincerest
apology.
Roland
- Next message: youssef sabri: "creating users"
- Previous message: jbatten: "FRS not starting"
- In reply to: Lanwench [MVP - Exchange]: "Re: Network printer"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Network printer"
- Reply: Lanwench [MVP - Exchange]: "Re: Network printer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
