EFI Fiery, Configuration And Setup

Page: 13 / 55

C
ONNECTING TO THE
N
ETWORK
13
Network Server Setup requirements
This section provides basic information about configuring the Fiery Controller and using
it on the network. It does not explain network functions for printing in general. Only
information specific to the Fiery Controller is presented. Setting up the network environment
correctly requires the presence and active cooperation of the network administrator. Detailed
instructions for configuring networks is beyond the scope of this document. For information,
see the documentation that accompanies your network.
Configure the network and servers, and ensure that there is a live network connection before
you configure Fiery Controller network settings in Setup. This allows the Fiery Controller to
query the network for zones, servers, and server-based queues.
Whenever you change the configuration of the Fiery Controller, printer, or network at your
site, alter the settings to correspond to the changed environment. Changing network or port
settings may require that you make changes to other Setup options, as well.
Windows networks
• The Fiery Controller requires a valid IP address, subnet mask, and gateway address.
Enter these addresses manually or use DHCP or BOOTP protocols to assign them
dynamically. Make sure the Fiery Controller name and address are listed in a domain name
server (DNS) or hosts name database used by your system.
If more than one Fiery Controller print connection is published (for example, if both the
Print queue and the Hold queue are published), consider creating a printer for each print
connection, so that users can print to each connection directly.
• Configure the Fiery Controller with the correct Windows domain name.
This is especially important for Windows printing, also known as SMB printing.
To use Microsoft Active Directory, you must assign the Fiery Controller to a domain. If
you assign the Fiery Controller to a workgroup, you cannot use Active Directory.