Configuring Netware Bindery Emulation; Confirming Bindery Context - Ricoh fax3310l Basic Features

Note: The Preferred File Server applies only to bindery-based queues. There is no effect on
NDS queues.

4.2 Configuring NetWare Bindery Emulation

NetWare 4.x can operate in two modes:
• NetWare Directory Services (NDS)
• Bindery Services Emulation
For NDS, refer to Section 4.3 Configuring the Network Interface Board.
These services run simultaneously and transparently to each other. You can configure the
Network Interface Board to operate with Bindery Services Mode only or to operate under
NDS. When configured under NDS, the Network Interface Board also services older file
servers operating in Bindery Mode.
Note: If the Network Interface Board is not properly set up for NDS and the Bindery Ser-
vices Mode is not running, the Network Interface Board cannot find its file servers.
The status page then indicates the NetWare protocol is not active.

4.2.1 Confirming Bindery Context

Before installing the Network Interface Board on a Novell NetWare 4.x server in Bindery
Emulation Mode, check that the server has a Bindery Context (name for the server under
Bindery Services Mode). If the server does not have a Bindery Context, you can install the
Network Interface Board in NDS mode. If the Network Interface Board must be installed
in Bindery Emulation Mode, the server must have a Bindery Context.
At the system console on the 4.x server, enter the load install command.
1.
Choose Maintenance/Selective Install from the menu.
2.
3. Choose NCF Files Options from the menu.
Choose Edit AUTOEXEC.NCF from the menu.
4.
5. Search the file to see if you have a statement similar to the following:
where context is the name of your file server context. If this string is not present,
you can enter it in the
NetWare Configuration
SET BINDERY CONTEXT=0U=
autoexec.ncf
4.2 Configuring NetWare Bindery Emulation
context
file.
4-7