Filter
Top Products
6
Settings for NetWare Server 133
6
6
6
6
6
6
6
6
6
6
6
Instructions for Using NetWare
Printing a text file
When you print a text file using the NPRINT command of
NetWare or DOS, redirection, misconversion or a gap in
characters may occur depending on the client environment.
IPX routing protocol “NLSP”
It is possible to set the IPX routing protocol “NLSP” from
NetWare 4.x or later; however, the print server 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 print server 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
WinAssist 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 print server for bindery mode, use
Novell IntranetWare Client or EpsonNet WebAssist (requires
a TCP/IP connection).
See your NetWare documentation for more information.