to use *native* (not 3rd-party) network printing, do you
*have* to have the 3000 in question using dns?  or should
the system be able to figure out how to 'find' the printer
by putting an entry into nsdir?  i've done the later (nsdir
route) but i'm getting the following on the console:

L0149#14:36/98/Output spooler, LDEV #80:  Domain name
resolver return status
nodename is unknown (HOST_NOT_FOUND).  Printer nodename
lookup failed.
Native Mode Spooler message 9665

14:36/98/Output spooler, LDEV #80:  Cannot communicate with
network printer.
Check network xport config, NPCONFIG.PUB.SYS, xport and
links started status,
intermediate network, and printer status.
Native Mode Spooler message 9662

+ = + = + = + = + = + = + = + = +

here's the npconfig file:
#====================================================================

# File: NPCONFIG
#====================================================================

global (setup_file = BLANK.PUB.SYS  # LaserJet 4Si setup
file.
        message_interval = 60       # Repeat msgs every >=
60 secs.
        banner_header = FALSE       # No leading banner page

        banner_trailer = FALSE      # No following banner
page.
        pjl_supported = FALSE       # LJ4Si is a full PJL
device.
        jam_recovery = TRUE)        # Reprints jammed pages
by itself.

80     (network_address = s0675p09) # Network printer at CRX
(675)

i can ping s0675p09 from nettool.  i also fired up inetd
(with all the appropriate /etc/ links in place...) to test
telnetting to this printer (actually an external jet
direct).  it worked fine.  but still no printing joy :-(
have i missed something?  or is dns the answer?
- d

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

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