IBM 4400-006 User Manual - Page 146

Novell Ethernet Interface Configuration (10/100Base-T), Preferred File Server (NDS and Bindery Setups)

Page 146 highlights

Chapter 7 Novell Ethernet Interface Configuration (10/100Base-T) Novell Ethernet Interface Configuration (10/100Base-T) SMART There are no mandatory Novell settings needed before the print server can be detected on the network. However, there can be some mandatory settings needed before a Novell print queue can be serviced by the Ethernet Interface. These mandatory settings are covered separately for Netware 3.x, 4.x and 5.x under the Host Configuration heading. The print server setup in a Novell environment is much simpler than that required in a TCP/IP one. No addresses, masks, or router entries are necessary and, in most cases, the Ethernet Interface can simply be connected to the network, turned on, and then configured for printing from a Novell station through PCONSOLE or Netware Administrator. However, there are some optional parameters you may wish to change, such as the preferred file server(s), print server password, polling time, frame type, print server name, NDS context, and NDS preferred tree. The following sections describe these optional parameters. Preferred File Server (NDS and Bindery Setups) In a bindery setup, the preferred file server specifies the file server on which the print server object was created. In an NDS setup, it specifies a file server on which the print server object resides. Since NDS is distributed, most administrators will not know which file server(s) the print server object is actually stored on, so in most NDS environments this option is not used. This feature is useful in a large Novell network, so that the Ethernet Interface does not ignore important file servers. If you are setting up the Ethernet Interface to work with a Bindery file server, it is a good idea to set a preferred server on the Ethernet Interface. To view which file servers the Ethernet Interface does acknowledge at a given time, use the debug nest fserver command. For more information, see "Complete Command List" on page 260. 146

  • 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
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326

Chapter 7
Novell Ethernet Interface Configuration (10/100Base-T)
146
Novell Ethernet Interface Configuration (10/100Base-T)
SMART
There are no mandatory Novell settings needed before the print
server can be detected on the network. However, there can be
some mandatory settings needed before a Novell print queue can
be serviced by the Ethernet Interface. These mandatory settings
are covered separately for Netware 3.
x
, 4.
x
and 5.
x
under the Host
Configuration heading.
The print server setup in a Novell environment is much simpler than
that required in a TCP/IP one. No addresses, masks, or router
entries are necessary and, in most cases, the Ethernet Interface
can simply be connected to the network, turned on, and then
configured for printing from a Novell station through PCONSOLE or
Netware Administrator.
However, there are some optional parameters you may wish to
change, such as the preferred file server(s), print server password,
polling time, frame type, print server name, NDS context, and NDS
preferred tree. The following sections describe these optional
parameters.
Preferred File Server (NDS and Bindery Setups)
In a bindery setup, the preferred file server specifies the file server
on which the print server object was created. In an NDS setup, it
specifies a file server on which the print server object resides.
Since NDS is distributed, most administrators will not know which
file server(s) the print server object is actually stored on, so in most
NDS environments this option is not used. This feature is useful in a
large Novell network, so that the Ethernet Interface does not ignore
important file servers. If you are setting up the Ethernet Interface to
work with a Bindery file server, it is a good idea to set a preferred
server on the Ethernet Interface.
To view which file servers the Ethernet Interface does acknowledge
at a given time, use the
debug nest fserver
command. For more
information, see “Complete Command List” on page 260.