IPX routing protocol “NLSP”
It is possible to set the IPX routing protocol “NLSP” from NetWare 4.x or later; however, the
network interface does not support NLSP. RIP/SAP controls the communication.
You can select the routing protocol from a) NLSP with RIP/SAP Compatibility, or b) RIP/SAP
Only. If you remove the bind of RIP or SAP when NLSP with RIP/SAP Compatibility is specified,
the network interface then cannot communicate with the file server and NDS. (See “Protocols” and
“Bindings” in NetWare’s INETCFG utility.)
Bindery and NDS
❏
You can check the bindery context path from the server console by using the SET BINDERY
CONTEXT command.
❏
If the bindery context path has not been set, or if you want to use the printing environment of
another context from a non-NDS client, you need to specify the context for the bindery
context. Use the SET BINDERY CONTEXT command to set the context in the
AUTOEXEC.NCF file.
❏
You cannot use the bindery print server mode with EpsonNet Config if you are running Novell
Client for Windows 95/98 version 3.00 or Novell Client for Windows NT version 4.50. To
configure the network interface for bindery mode, use Novell IntranetWare Client or
EpsonNet Config with Web Browser.
See your NetWare documentation for more information.
Time required to recognize the network interface
It takes up to two minutes for the NetWare server to recognize the network interface, after the
printer is turned on. During this start-up time, the status sheet does not show the correct information.
Frame type
The same frame type should be used for the NetWare server and IPX router on the same network.
If more than one frame type is used on the same network, bind all the frame types to the NetWare
servers and IPX routers.
For NetWare 5.x
The IPX protocol must be installed (bound) on the NetWare 5.x server.
EPSON Network Guide
How To
74
