Kyocera Ai5555 NC-2 Instruction Hand Book - Page 71

Con Using NetWare 4.x Bindery Emulation

Page 71 highlights

NetWare Configuration Configure Using NetWare 4.x Bindery Emulation Overview Novell's NetWare 4.0x can operate in the Bindery Services Emulation mode and NetWare Directory Services (NDS) mode (see NetWare Directory Services to configure the print server in this mode). While Bindery Emulation services and NDS services run simultaneously and transparently to each other, the print server may be configured to operate with Bindery Services mode only, as described in this section; or with NDS only. When configured under NDS, the print server will also service older file servers operating in bindery mode. NOTE: If the Bindery Services mode is not running, the print server will be unable to find its file servers, and the status page will indicate that the Novell NetWare protocol is not active. Before installing the print server on a Novell NetWare 4.x server in Bindery Emulation mode, first check to be sure the server has Bindery Context by using the Confirming Bindery Context procedure on the next page. If the server does not have Bindery Context, the Novell administrator must execute either a SET command from the console prompt, or, modify the AUTOEXEC.NCF file to include the proper SET command and restart the server. NOTE: The command entered from the console prompt takes effect immediately, whereas, the definition in the autoexec file takes effect only when the server is shut down and then restarted. 3-50 NetWare Configuration

  • 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

3-50 NetWare Configuration
NetWare Configuration
Configure Using NetWare 4.x Bindery Emulation
Overview
Novell’s NetWare 4.0x can operate in the Bindery Services Emulation mode
and NetWare Directory Services (NDS) mode (see
NetWare Directory
Services
to configure the print server in this mode).
While Bindery Emulation services and NDS services run simultaneously and
transparently to each other, the print server may be configured to operate
with Bindery Services mode only, as described in this section; or with NDS
only. When configured under NDS, the print server will also service older file
servers operating in bindery mode.
NOTE: If the Bindery Services mode is not running, the print server will be unable to
find its file servers, and the status page will indicate that the Novell NetWare protocol is
not active.
Before installing the print server on a Novell NetWare 4.x server in Bindery
Emulation mode, first check to be sure the server has Bindery Context by
using the
Confirming Bindery Context
procedure on the next page.
If the server does not have Bindery Context, the Novell administrator must
execute either a SET command from the console prompt, or, modify the
AUTOEXEC.NCF file to include the proper SET command and restart the
server.
NOTE: The command entered from the console prompt takes effect immediately,
whereas, the definition in the autoexec file takes effect only when the server is shut
down and then restarted.