Solaris 2.6 and NIS Considerations

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.

  ---

  Note -

  There CANNOT be another NIS printers.conf file on the same NIS domain; this confuses the Netra j printer administration.

  ---