Technical data

3-12 Setting up the Fiery X3 from a Windows Computer

IP Address (Ethernet)—Enter the Fiery X3 IP address for Ethernet. You must change

the default 127.0.0.1 to a valid address for your network. For information about

setting up printing with TCP/IP, see Chapter 4.

Subnet Mask (Ethernet)—If you need to set the subnet mask, enter one of the

following values:

• 255.0.0.0 if the IP address starts with a number less than 128

• 255.255.0.0 if the IP address starts with a number from 128 through 191

• 255.255.255.0 if the IP address starts with a number greater than 191

NOTE: Be sure to conﬁrm the subnet mask setting with your network administrator

before proceeding. In some cases the required setting may be different from those

listed.

Protocol Setup (Token Ring)

Enable on Token Ring—Select if you have a TCP/IP network connected to the

Fiery X3 over Token Ring. If you use Token Ring, enabling TCP/IP for Token Ring

is required for enabling the Fiery WebTools.

If you are using TCP/IP for printing from Windows NT 4.0 workstations, enabling

TCP/IP here also enables you to use Fiery utilities from Windows NT 4.0 worksta-

tions using TCP/IP protocols.

IP Address (Token Ring)—Enter the Fiery X3 IP address for Token Ring. You must

change the default to a valid address for your network.

IP Auto (Token Ring)—Click to allow the Fiery X3 to obtain its Token Ring

IP address by searching the network. Depending on your network and the protocol

you select (DHCP, BOOTP, or RARP), the IP address can change.

Select protocol (Token Ring)—Select the protocol over which the Fiery X3 should

search for its IP address. Both DHCP and BOOTP allow the Fiery X3 to obtain the

Token Ring IP address and Subnet Mask automatically. RARP obtains only the Token

Ring IP address.

Depending on your network, the Fiery X3 might be assigned a different address after

you reboot the Fiery X3. With the DHCP setting, the Fiery X3 can be assigned a dif-

ferent address even if it is not rebooted. Make sure the network is already conﬁgured

properly for the protocol you select.