This chapter describes how to configure print services on a Netra server.
The print services available include:
Netra j print services are focused towards systems where no prior print services are configured.The Netra GUI provides a clear and simple interface to configure Netra print services.
Local Printer Administration - Configure printers attached directly to the Netra Server's serial and/or parallel ports. This automatically configures the Netra server as a Solaris print server so that print jobs can be sent to the printer from the Netra server, or from clients anywhere on the network. As a print server, the Netra server is capable of scheduling, queuing, and printing jobs submitted to it either locally or from other clients on the network.
Network Printer Spooler - A Netra j server can be configured as a Network Printer Spooler. This allows the Netra Server to become a spool server for a network printer (a printer connected directly to the network via its own network adapter). A spool server is a server that accepts and manages print jobs from print clients and submits them to the network printer. In effect, the Netra j server acts as a printer server, as far as print clients are concerned.
The Network Printer Spooler feature is supported only on Netra j servers installed on Solaris 2.6. Netra j spool server capabilities apply only to new spool servers configured through the Netra administration interface, or spool servers configured according to the Solaris 2.6 documentation, (using the "netstandard" interface script).
Remote Printer Administration - You can configure the Netra server with access to remote printers elsewhere on the network. Remote printers can be either network printers, or printers attached to other Solaris or `bsd' print servers. The Netra Server can act as a print server with multiple local printers connected to it, while simultaneously accessing multiple remote printers.
Set Default Printer - When at least one printer is configured on the system, this link will appear. This allows the Netra Administrator to configure any of the local or remote printers to be the Netra j "default printer".
The print server is based on UNIX SVR4 LP print services, which ship with the Solaris 2.5.1 and 2.6 operating environments. The Netra server can print to SunOSTM 4.1.x (standard BSD printing), Solaris 2 and subsequent compatible releases (standard LP or SVR4 printing) remote print servers, and any network printer that conforms to these print models. It can also service requests sent from clients running SunOS 4.1.x, and Solaris 2 and subsequent compatible releases; since it also runs a BSD listener, it can receive jobs from remote hosts running Solaris 1, other types of UNIX, and any client capable of using the BSD print mechanism.
When installing Netra j software onto a system that is already configured with a local printer, or is already configured as a print network spooler to a network printer, caution is advised. Print services available to the Solaris environment include many third-party software packages. Netra should not interfere with existing network printer spoolers configured on the system prior to the Netra j software installation. However, continue to administer these printers with the third- party administration tool, rather than through the Netra j interface.
When installing Netra j software onto a system that is already configured for access to remote printers, you can safely administer this printer access from the Netra j interface.
On Netra j servers that are running the Solaris 2.6 operating environment, printer administration behaves slightly differently, depending on whether the Netra j server is configured as a NIS client or as a NIS master server.
NIS client
As a NIS client, the Netra j administration interface displays a list of printers configured ONLY on the local system. Any information about remote printers and print servers that is broadcast by a remote NIS server is not displayed through the Netra j administration interface. However, such printers are still available for printing from the Netra j server using standard Solaris commands.
As a NIS client, the Netra j server does not broadcast its /etc/printers.conf file as a NIS printers.conf.byname map.
One method NCs use to access printers is by specifying a NIS printers.conf.byname map. Since no such map exists on the Netra j server when configured an a NIS client, the NCs can NOT use this method to access the Netra j locally configured printers. An alternative method does exist (see the printing properties section in the JavaStation Client Software Guide) where you explicitly specify the server name and printer name. In this case, the server name is the name of the Netra j server, and the printer name is the name of the locally configured printer.
To provide access to the Netra j printers, include information about those printers in the network NIS server printers.conf file. That way, the NCs can use all NIS printers, which will include the printers configured locally on the Netra j server.
NIS master server
As a NIS master server, the Netra j server makes the etc/printers.conf file into a NIS map so that NCs and other clients on the same NIS domain have access to the Netra j printer configuration information.
There CANNOT be another NIS printers.conf file on the same NIS domain; this confuses the Netra j printer administration.
From the Main Administration page, under "Network Service Administration," click Printer Administration.
Under "Local Printer Administration," choose one of the following:
Add Printer to Serial Port a
Add Printer to Serial Port b
Add Printer to Parallel Port
Complete the form using the information in the following tables.
Table 6-1 Printer Characteristics
Option |
Description |
---|---|
Printer Name |
Enter a printer name with up to 14 characters (A-Z, a-z, 0-9,-,_). Do not start the printer name with "-" or "_". |
Printer Type |
Choose PostScript, ASCII, HP (PCL ASCII), HP(PCL), or Unknown for a printer that is not listed. See Table 6-2 for more detail. |
File Contents |
Choose PostScript, ASCII, or Any. Use Any for a printer that is not PostScript or ASCII. |
Fault Notification |
Choose Console (print fault messages to console), Root Mail (email fault messages to root), or none (do not send fault notification messages). |
Description (optional) |
Enter an optional description of the printer (up to 28 characters). |
Enable BannerControl? |
Specify whether banner page control is enabled. |
Table 6-2 Printer and Content Type
Printer Type |
Content Type |
---|---|
PostScript |
PostScript |
ASCII |
ASCII |
HP Laserjet (PCL ASCII) |
ASCII |
HP Laserjet (PCL) |
ASCII |
Unknown (All other printers) |
Any |
When adding a printer to a serial port, also specify the serial port baud rate, parity, and character size to match those of the printer.
Table 6-3 Serial Port Attributes
Option |
Description |
Baud Rate |
Choose 9600, 19200, or 38400. |
Parity |
Choose none, even, or odd. |
Character size |
Choose 7 bits, or 8 bits. |
Click OK.
From the Main Administration Page, under "Network Service Administration," click Printer Administration.
Under "Local Printer Administration," choose one of the following:
Choose from the following options:
Modify or Delete Printer Printer name attached to Serial Port a
Modify or Delete Printer Printer name attached to Serial Port b
Modify or Delete Printer Printer name attached to Parallel Port
If you do not know what printer type and file content type to use, or if you think that your printer is not one of the specified types, then choose Printer Type: Unknown and Content Type: Any. Then Netra makes no assumptions about the printer or the files being printed. However, if you are sure that your application is submitting a print job of the correct format to the printer, it should print without trouble.
This option is only for servers that run on the Solaris 2.6 operating environment.
This option enables the Netra j server to be set up as a network printer spooler. This means that the Netra j server accepts, queues, and manages print jobs for a network printer (in other words, a printer with a built-in network adapter attached directly to the network with its own host name and IP address).
Configuration is compatible with new functionality added to the LP print model for Solaris 2.6, and uses the new "netstandard" interface script developed for Solaris 2.6 to manage Network Printers.
Netra j does not display third-party printer configurations. Any existing or subsequently configured third-party network spoolers on a Netra j server need to be managed through the supplied third-party software. Netra j Printer Administration does NOT interfere with third-party printer configurations.
Currently, the Network Spooler form prompts for Network Printer Access Name. There is no default format for this field; it is dependent on the printer model and network configuration. In most cases, and in the case of TCP/IP networks in particular, enter either the printer name, or IP address of the network printer in this field. This is most likely sufficient information to establish connectivity with the printer. Some printers can require specification of a TCP port number also. In this case, after the printer name or IP address, add a colon (:), followed by the port number. If difficulties remain, contact the printer manufacturer regarding the correct format of the Network Printer Access Name.
From the Main Administration Page, under "Network Service Administration," click Printer Administration.
Under "Network Printer Spooler Administration," click Add Network Printer Spooler.
Complete the form using the information in the following table.
Table 6-4 Network Printer Spooler Attributes
Option |
Description |
---|---|
Printer Name |
Enter a printer name with up to 14 characters in the range (A-Z, a-z, 0-9,-,_). Do not start the printer name with "-" or "_" |
Network Printer Access Name |
Enter the Network Printer Access Name. Usually this is the same as the printer name, or the IP address of the printer. However, there is no default format for this field. Contact the printer vendor for the correct format of this field if difficulties arise. |
Protocol |
Set the over-the-wire protocol used to communicate with the printer. Both BSD and raw TCP are supported. |
Retry timeout |
Sets the retry timeout value that represents a number of seconds to wait between attempting connections to the printer. |
Printer Type |
Choose PostScript, ASCII, HP (PCL ASCII), HP (PCL), or Unknown for a printer that is not listed. |
File Content type |
Choose PostScript, ASCII, or Any for a printer that is not PostScript or ASCII. |
Fault Notification |
Specify how printer error messages are treated. Choose Console (print fault messages to console), Root Mail (email fault messages to root), or none (do not send fault notification messages). |
Description (optional) |
Enter a description of the printer (up to 28 characters). |
Enable Banner Control |
Enable/Disable the ability of the user print command to specify whether a banner page is printed. |
From the Main Administration Page, under "Network Service Administration," click Printer Administration.
Under "Network Printer Spooler Administration," choose one of the following:
To modify a network printer spooler, click Modify for the appropriate spooler, and make changes in the form using Table 6-4 as a reference.
To delete a network printer spooler, click Delete for the appropriate spooler, then confirm the operation.
Remote Printer Administration provides a way of adding access to remote printers on the Netra j server. Any remote printer configured through the Netra j administration interface is added to the local printer configuration files.
For a Netra j server installed on Solaris 2.6, and configured as a NIS client, a remote NIS server may be already broadcasting remote printer access for certain printers. In this case, Netra j detects the presence of such printers, and DOES NOT allow them to be configured again through the Netra j administration interface. This would lead to potential inconsistencies in information stored in the local printer configuration file with that being broadcast by the remote print server. Even though you cannot configure such printers through the Netra j administration interface, access to print to the remote printers is still available in the normal way and to all applications. To convince yourself that these printers are available, execute the command lpstat -v on a shell command line.
From the Main Administration Page, under "Network Service Administration," click Printer Administration.
Under "Remote Printer Administration," click Add access to Remote Printer.
Complete the Add Remote Printer form using the information in the following table.
Table 6-5 Remote Printer Attributes
Click OK.
From the Main Administration Page, under "Network Service Administration," click Printer Administration.
Under "Remote Printer Administration," choose one of the following:
To modify a remote printer, click Modify for the appropriate printer, and make changes in the form using Table 6-5 as a reference.
To delete a remote printer, click Delete for the appropriate printer, and then confirm the operation.
When at least one local or remote printer has been configured on the system, the `Set Default Printer' option is available on the Printer Administration main page.
Netra printer administration sets a system-wide default printer.
However, there are a number of ways for individual users to override this value: by using a ~/.printers file; by setting the LPDEST environment variable; or by setting the PRINTERS environment variable. Once any of these are set, an lpstat -d reveals their value for the default printer, not the one quoted in /etc/printers.conf.
If the system contains a /etc/printers.conf file, and there is also a NIS printers.conf file available, the NIS default value may be the one used.
If the user unsets the LPDEST, PRINTERS variables and removes the ~/.printers file, then the Netra setting of default printer is the one quoted by lpstat -d.