Re: adding network printer to system
From: SuperGumby [SBS MVP] (not_at_your.nellie)
Date: 03/27/05
- Next message: 652Wowway: "Re: Step by Step Guide for RWW"
- Previous message: 652Wowway: "Re: Step by Step Guide for RWW"
- In reply to: Bernie Hunt: "Re: adding network printer to system"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 27 Mar 2005 12:54:30 +1000
I prefer to allow the printer to get an IP by DHCP.
When the printer has acquired an IP by DHCP you can view the status in the
DHCP console, this allows you to inspect the MAC address and create a DHCP
reservation for the printer.
I prefer to load drivers on the server but...
Many (HP are finally giving you a damned choice) printers come with a CD
which loads not only drivers but every piece of useless junk under the sun.
I tell myself three times (because I've been bitten SO MANY times in the
past) 'I will NEVER put the CD that comes with a printer into a server until
I have _at least_ run it on a workstation but preferrably run it against a
test server'. What's the use of an 'ink level monitor' running on the server
no-one except me on my occassional visit looks at?
I'll search the CD for directories containing .inf files.
If I can't find them I'll try to open every lousy executable on the thing
with WinZip, see if the BARE drivers are hidden somewhere inside.
I'll visit the manufacturers website and as soon as I see 'order the CD'
instead of 'download simple driver' I'll add that piece of s&^t to the list
of 'once bought, never again', I've deforrested most of South America
maintaining that list.
GO ON, start me about MFC devices!!! PUSH MY BUTTON!!!
Thankfully, some printer manufacturers realised all along and others are
finally waking up. Printers which get used on networks require a driver,
often drivers for other OS's, not some funky 'help me print my document'
program.
Even with bare drivers there can be a downside to sharing network attached
printers from the server. Of course, it's a driver issue. If the
manufacturer doesn't take enough care designing the driver it can bring your
server to a halt, often a restart of the spooler process will fix it but
often enough it won't. If you load drivers on the workstation to talk
directly to the printer(s) you are less likely to have to shutdown your
business while the server restarts because a two page word document was TOO
COMPLEX for their lousy driver.
Still, I prefer to attach to the network device from the server, load
additional drivers, share.
"Bernie Hunt" <bhunt@optonline.net> wrote in message
news:ORMmnGnMFHA.3228@TK2MSFTNGP12.phx.gbl...
> My experience with network printers is to do the following. Assign the
> printer an IP, do not let is get one from DHCP. Install the printer on the
> server and share the printer. Then from the workstation, add a network
> printer and drill down to the server and the shared printer. This works
> well for me for a couple of reasons, it keeps the printers from moving
> around IP wise. It also makes it much easier with some printers that
> require the CD to install on each workstation. Specifically the OKIData
> color lasers. Its a pain to carry the disk around to each workstation, but
> if it's shared off the server, the server will download the drivers to the
> workstation.
>
> Also make sure you block out a section of IPs for the printers. I
> generally put the router/gateway at 1, 2-10 for fixe IP printers, 11-20
> for fixed IP servers and 21-255 is available for DHCP. Nothing offical but
> just what works for me and keeps all my networks the same.
>
> Bernie
>
> "Bryce" <fukuzzz@takethisout.hotmail.com> wrote in message
> news:%23mvazK9LFHA.3296@TK2MSFTNGP15.phx.gbl...
>> When I add ip address printers to the network, what is the proper way to
>> do
>> it?
>>
>> They have printers here that connect to computers and are shared and then
>> some that are standalone with printerservers on them.
>>
>>
>> This question has to do with the printerserver type that has it's own ip
>> address.
>>
>> Do I add the printer with the server and then share it there first?
>>
>> Can I do it from a client and share it there?
>>
>> What are the proper steps for adding a network printer?
>>
>> I run into so many problem with these. Sometimes people can get to them,
>> sometimes they can't. Then, mysteriously, I have to reinstall the dang
>> things.
>>
>> When I add them, I have the box checked "include in directory".
>>
>> When I had a printer later on, do I search for it by http://192.168.0.28
>> for
>> example or should I do the first one where it ask to search the directory
>> and type in the hp laserjet 2300wm for example?
>>
>> Is there a bad way, a good way, a better way and a best way to add
>> printers
>> to the network?
>>
>> Thanks.
>>
>> Bryce.
>>
>>
>
>
- Next message: 652Wowway: "Re: Step by Step Guide for RWW"
- Previous message: 652Wowway: "Re: Step by Step Guide for RWW"
- In reply to: Bernie Hunt: "Re: adding network printer to system"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
