David De Weerdt wrote:

> You normally can specify the IP address after the network_address variable,
> this way you have one location to look if there are problems

first, an update....  i was able to get the printer working by adding an entry
into hosts.net.sys.  (thanks greg!)  the system still isn't using pure dns
(it's a long story) but i guess it's big toe is dipped into the pool :-)

second, i received many comments -- like the one above -- about putting the ip
address of the printer into npconfig.  nearly all of my npconfig files are set
up that exact way.  *but* from a maintenance prespective, i think it's
preferable to have the dns name of the printer in the npconfig file.  if any
address changes, then you're scrambling to update your npconfig file(s).  *and*
if you're using a common class name for your network printers, then spooling
has to be stopped on all your similarily named printers just to correct the ip
address of one printer.  it's subtle.  it's certainly not mentioned (that i can
find) in the communicator.  i frankly can't remember how i came up with the
idea....   comments?                  - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<