Kyocera KM-C2030 Fiery X3e Configuration Guide for Ver 2.0 - Page 27

Configuring a WindowsNT4.0/2000 server to communicate with theFieryX3e

Get Kyocera KM-C2030 PDF manuals and user guides View all Kyocera KM-C2030 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

22-3 Fiery X3e on a TCP/IP network with Windows NT 4.0/2000/XP Configuring a Windows NT 4.0/2000 server to communicate with the Fiery X3e To configure a Windows NT 4.0/2000 server to communicate with the Fiery X3e, follow these general steps. More detail is provided in subsequent sections in this chapter and in your Microsoft documentation. • Load the TCP/IP network protocol on the server and configure it with an IP address, subnet mask, and gateway. • Enter the host name of the Fiery X3e in the host database used by your system (see page 2-4). • Perform Fiery X3e Setup. • On the Windows NT 4.0/2000 server, create a printer for each Fiery X3e print connection, install the appropriate printer drivers, and (optionally) share the printer on the network (see page 2-4). • Enter the host name and remote printer name of the Fiery X3e in the printer connection. For more information, see page 2-17. • If the Windows NT 4.0/2000 server is also a workstation, install Fiery utilities (see the User Software Installation Guide). Adding the Fiery X3e to the TCP/IP network If your TCP/IP network consists of Windows NT 4.0/2000 servers, and Windows NT 4.0/2000/XP clients, follow the procedures in this section. If the network also includes UNIX workstations, see the procedures on page 2-17.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
2
2-3
Fiery X3e on a TCP/IP network with Windows NT 4.0/2000/XP
Configuring a Windows NT 4.0/2000 server to communicate with
the Fiery X3e
To configure a Windows NT 4.0/2000 server to communicate with the Fiery X3e,
follow these general steps. More detail is provided in subsequent sections in this
chapter and in your Microsoft documentation.
•
Load the TCP/IP network protocol on the server and configure it with an IP address,
subnet mask, and gateway.
•
Enter the host name of the Fiery X3e in the host database used by your system (see
page 2-4
).
•
Perform Fiery X3e Setup.
•
On the Windows NT 4.0/2000 server, create a printer for each Fiery X3e print
connection, install the appropriate printer drivers, and (optionally) share the printer
on the network (see
page 2-4
).
•
Enter the host name and remote printer name of the Fiery X3e in the printer
connection. For more information, see
page 2-17
.
•
If the Windows NT 4.0/2000 server is also a workstation, install Fiery utilities (see
the
User Software Installation Guide
).
Adding the Fiery X3e to the TCP/IP network
If your TCP/IP network consists of Windows NT 4.0/2000 servers, and
Windows NT 4.0/2000/XP clients, follow the procedures in this section. If the
network also includes UNIX workstations, see the procedures on
page 2-17
.