Kyocera KM-C2230 Fiery X3e 22C-KM Configuration Guide for KM-C2230 - Page 34

Configuring a NetWare server for printing, Setting up Network Servers

Page 34 highlights

22-10 Setting up Network Servers You do not need to rerun Setup when you add or remove a NetWare queue; however, you should restart the Fiery X3e after you create or remove a queue. When the Fiery X3e is configured to connect to a NetWare server, it polls the NetWare server for jobs in each of its queues. If jobs are found, they are automatically transferred over the network to the matching connection on the Fiery X3e. For example, jobs from the NetWare queue with the _print extension are sent to the Fiery X3e Print queue. While a job is processed and printed, a record of the job is being created. You can access the Job Log containing these records at any time. Configuring a NetWare server for printing The following sections explain how to set up a NetWare file server so networked users can print to the Fiery X3e from their workstations, and the Fiery X3e can obtain print jobs from the NetWare server. For each NetWare file server that you configure, follow these general steps. More detail is provided in subsequent sections and in your NetWare documentation. • Make sure the server is connected to a functioning IPX network. • Log in as the Supervisor on a PC connected to the NetWare file server. • For NetWare installations, set up an NDS connection (see page 2-12). • For NetWare in emulation mode, set the bindery context (see page 2-12). • For NetWare in bindery emulation, set up a file server, print server, and print queue for the Fiery X3e (see page 2-13). With bindery services, you can route all Fiery X3e print jobs through the same NetWare file server, or you can configure more than one file server to handle Fiery X3e jobs. The functions you perform on the Novell server, the Fiery X3e, and the client workstation are summarized in the following tables. The first table applies to NDS connections, and the second to bindery connections. Complete the operations in the left column, then the center column, then the right column.

  • 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
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190

2
2-10
Setting up Network Servers
You do not need to rerun Setup when you add or remove a NetWare queue; however,
you should restart the Fiery X3e after you create or remove a queue.
When the Fiery X3e is configured to connect to a NetWare server, it polls the NetWare
server for jobs in each of its queues. If jobs are found, they are automatically transferred
over the network to the matching connection on the Fiery X3e. For example, jobs
from the NetWare queue with the
_print
extension are sent to the Fiery X3e Print
queue. While a job is processed and printed, a record of the job is being created. You
can access the Job Log containing these records at any time.
Configuring a NetWare server for printing
The following sections explain how to set up a NetWare file server so networked users
can print to the Fiery X3e from their workstations, and the Fiery X3e can obtain print
jobs from the NetWare server.
For
each
NetWare file server that you configure, follow these general steps. More detail
is provided in subsequent sections and in your NetWare documentation.
Make sure the server is connected to a functioning IPX network.
Log in as the Supervisor on a PC connected to the NetWare file server.
For NetWare installations, set up an NDS connection (see
page 2-12
).
For NetWare in emulation mode, set the bindery context (see
page 2-12
).
For NetWare in bindery emulation, set up a file server, print server, and print queue
for the Fiery X3e (see
page 2-13
).
With bindery services, you can route all Fiery X3e print jobs through the same
NetWare file server, or you can configure more than one file server to handle
Fiery X3e jobs.
The functions you perform on the Novell server, the Fiery X3e, and the client
workstation are summarized in the following tables. The first table applies to NDS
connections, and the second to bindery connections. Complete the operations in the
left column, then the center column, then the right column.