I had asked how one goes about managing network printers with SunSoft Print
Client (SSPC)/NIS+ (Detailed question attached). It turns out that the true
problem is specifying a print queue for a print server. The Solstice AdminSuite
print manager does not permit the entry of a print queue when specifying a
remote printer. One CAN configure this indirectly by naming the global print
queue the same name as the print queue on the print server. This breaks down if
you have two servers with printers using the same print queue name, as is the
case at my customer's facility.
Having had success with this technique, though, I started poking around the FNS
command line tools and fncreate_printer in particular. The documentation for
fncreate_printer, FNS in general, and specifically the manner in which SSPC uses
FNS is quite vague to be generous. After some exploration, though, I came up
with a solution that appears to work! Let me share this so others can take
advantage of the benefits of central administration of printers via SSPC.
The basic command line for adding a printer foo, and print queue bar, as print
queue name lexmark to the namespace used by SSPC is:
fncreate_printer thisens/service/printer lexmark bsdaddr=foo,bar
This command does not attach a description to the printer nor does it setup a
printer as the default printer. I accomplished these tasks by running the
Solstice AdminSuite print manager after performing all necessary
fncreate_printer commands, selecting and filling in printer descriptions and
selecting the default printer box for the desired printer. One problem with this
is that the print manager hangs after updating a description on a networked
lexmark. I believe this is because it is expecting the printer to have more
"intellegence" than it actually has, and thus a protocol exchange it attempts as
part of the update fails. The bottom line, though, is that modifying a printer
does not loose the discrete definitions of print server, print server queue, and
global print queue while updating these other items.
Followup questions are:
1. Are any of these issues corrected in more recent versions of Solaris or
Solstice AdminSuite? I am currently running Solaris 2.5 and the AdminSuite
bundled with it.
2. How would one migrate this SSPC configuration to a new Solaris 2.6 server
with the version of AdminSuite bundled into it? I will have to do this within
the next few weeks or so.
Finally, my thanks for the few responses I recieved. While they did not
specifically solve the problem, they pointed me in directions that eventually
lead to the solution I've described:
Derek_Eichele@aimfunds.com (Derek Eichele)
wilhelm@lexmark.com
birger@Vest.Sdata.No (Birger A. Wathne)
-Marc
Marc S. Gibian
COMSYS Information Technology Services phone: (617) 377-6350
PRISM/TFS email: gibian@stars1.hanscom.af.mil
or is it: gibian@hanscom.af.mil
well, maybe: gibianm@hanscom.af.mil
and if all else fails: marc.gibian@acm.org
--Boundary_(ID_0e5g2BxBc8RPsYEnug53Yg)
Content-type: MESSAGE/RFC822
Content-description: Mailbox
Content-MD5: PP+GsyDygT5ptC/jKeYjpg==
X-Sun-Data-type: mail-message
Return-path: <sun-managers-relay@ra.mcs.anl.gov>
Received: from stars1.hanscom.af.mil by drizzle.tfs.com (SMI-8.6/SMI-SVR4)
id QAA07593; Thu, 20 Nov 1997 16:20:34 -0500
Received: from smtpgw.hanscom.af.mil by stars1.hanscom.af.mil
(SMI-8.6/SMI-SVR4) id QAA10138; Thu, 20 Nov 1997 16:13:32 -0500
Received: from ra.mcs.anl.gov by smtpgw.hanscom.af.mil (SMI-8.6/SMI-SVR4)
id QAA08124; Thu, 20 Nov 1997 16:15:46 -0500
Received: from localhost (daemon@localhost) by ra.mcs.anl.gov (8.8.3/8.8.3)
with SMTP id NAA29172; Thu, 20 Nov 1997 13:39:56 -0600 (CST)
Received: by ra.mcs.anl.gov (bulk_mailer v1.5); Thu, 20 Nov 1997 13:39:29 -0600
Received: (from daemon@localhost) by ra.mcs.anl.gov (8.8.3/8.8.3)
id NAA29121 for sun-managers-outbound; Thu, 20 Nov 1997 13:01:08 -0600 (CST)
Received: (from listserv@localhost) by ra.mcs.anl.gov (8.8.3/8.8.3)
id NAA29114 for smmsgs-out; Thu, 20 Nov 1997 13:01:03 -0600 (CST)
Received: from smtpgw.hanscom.af.mil (smtpgw.hanscom.af.mil [129.53.1.252])
by ra.mcs.anl.gov (8.8.3/8.8.3) with SMTP id NAA29108 for
<sun-managers@ra.mcs.anl.gov>; Thu, 20 Nov 1997 13:00:33 -0600 (CST)
Received: from stars1.hanscom.af.mil by smtpgw.hanscom.af.mil
(SMI-8.6/SMI-SVR4) id OAA02476; Thu, 20 Nov 1997 14:00:38 -0500
Received: from drizzle.tfs.com by stars1.hanscom.af.mil (SMI-8.6/SMI-SVR4)
id NAA08851; Thu, 20 Nov 1997 13:58:15 -0500
Received: from hail.tfs.com by drizzle.tfs.com (SMI-8.6/SMI-SVR4)
id OAA07021; Thu, 20 Nov 1997 14:05:14 -0500
Received: by hail.tfs.com (SMI-8.6/SMI-SVR4) id OAA19887; Thu,
20 Nov 1997 14:04:22 -0500
Date: Thu, 20 Nov 1997 14:04:22 -0500
From: gibian@stars1.hanscom.af.mil (Marc S. Gibian)
Subject: Network print configuration for Lexmark network printers
Sender: sun-managers-relay@ra.mcs.anl.gov
To: sun-managers@ra.mcs.anl.gov
Reply-to: gibian@stars1.hanscom.af.mil (Marc S. Gibian)
Message-id: <199711201904.OAA19887@hail.tfs.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-MD5: nyTrlmVr/4hRInNgQXW88g==
Precedence: bulk
Content-length: 2203
>From gibian@stars1.hanscom.af.mil Thu Nov 20 16:20:35 1997
Followup-to: gibian@stars1.hanscom.af.mil (Marc S. Gibian)
Status: RO
I have a group of Solaris 2.5 workstations running the SunSoft Print Client
(SSPC) to allow centralized configuration of printing via NIS+. One of these
machines has been hosting a NeWSprinter 20 via the NeWSprint software product,
and all others are configured via SSPC to print to the system hosting the
NeWSprinter. I need to retire the system hosting the NeWSprinter. Rather than
move the NeWSprinter to a different machine, I want to retire it as well (All
these systems will be migrating to Solaris 2.5.1 or 2.6 and thus I don't want to
deal with the dropped support of NeWSprint... I'm also tired of fighting for
money everytime we run out of NeWSprinter toner, you can buy a nice modern laser
printer of greater quality for the cost of just a few NeWSprinter toner
cartridges). There are a number of Lexmark printers available on our network. I
am able to locally configure my systems to print to them using the following set
of commands:
with lexmark being the numeric ip address of the printer or a resolvable
hostname for that printer...
lpsystem -t bsd lexmark
lpadmin -pprintername -slexmark!PORT1
lpadmin -pprintername -I any
enable printername
accept printername <appears to be redundant, but it can't hurt>
I have tried to find a way to configure printing in this way via Solstice
AdminSuite's print manager, but can't find a way to specify the PORT1 component.
I also tried configuring one host for printing to the lexmark printer and then
using AdminSuite to setup remote printing from all other systems to the one with
the lexmark configured, but that fails with an error (something like "not a
printer local to <hostname>"). I really don't want to have to locally configure
the lexmark printers on every machine I administer, so...
Does anyone know how I use SSPC/NIS+ to configure printing to these lexmark
network printers?
TIA,
Marc
Marc S. Gibian
COMSYS Information Technology Services phone: (617) 377-6350
PRISM/TFS email: gibian@stars1.hanscom.af.mil
or is it: gibian@hanscom.af.mil
well, maybe: gibianm@hanscom.af.mil
and if all else fails: marc.gibian@acm.org
--Boundary_(ID_0e5g2BxBc8RPsYEnug53Yg)--