Lantronix ETS Reference Manual - 2.9 Netware
NetWare
Concepts
2-16
2.9 NetWare
Novell’s NetWare software allows you to link computers together and provide file and printer sharing. It is
typically used to network DOS-based PCs, but is starting to appear under UNIX and other operating
systems. NetWare is built around file servers, which handle user logins, provide network resources, and
control security. At least one file server, such as a PC or UNIX host, is required in any NetWare
environment. NetWare users typically have to log into a file server to enjoy the networked (shared) benefits.
The ETS supports a significant subset of the NetWare functionality, most notably print spooling. Fileservers
can be configured to send queued print jobs to printers attached to the ETS. No special software is required
on the fileserver; configuration uses the EZWebCon Configuration software or the standard PCONSOLE
utility. Any user or application that can use NetWare print queues can spool jobs to the ETS.
The ETS must periodically query the file servers for pending jobs. To do so, it logs into a file server to access
the print spooler, and will try to connect to all file servers on the local network (subject to access lists,
explained later) to check for such jobs. See Set/Define Server NetWare Loadhost on page 12-74 for more
information.
NetWare support includes an IPX COM port redirector that allows users on IPX networks to share modems.
For more information, see the Redirector Quick Installation Template that came with your ETS. NetWare
support also allows logins from fileservers to the ETS (for configuration) and file downloading (to
download the system software at boot time).
2.9.1 Networking
Each NetWare node uses its hardware address as its node ID. In addition, the ETS gets all the networking
information it needs from periodic broadcasts sent by NetWare routers on the network. It will learn its own
network number as well as routes to non-local file servers. No further configuration is needed.
The NetWare protocol can use all four Ethernet frame formats. It will listen for all frame formats, and then
use the correct one for the connection. The different frame types are treated as different networks, and thus
each frame type has a different network number. If there is only one frame format in use on the LAN, the
ETS will use the network number for that frame type. If there are multiple frame types, limitations to the
NetWare protocol require that the ETS use a different network number for each frame type on which it wants
to advertise itself.
The ETS can use multiple frame types by creating a new, unique “internal network number” and advertising
itself as a router to the internal network. Any nodes or fileservers that need to communicate with the ETS
use this new network number, and treat the ETS as a router to that network. If this behavior is not desired,
the ETS can be forced to use only one frame type (and thus not need an internal network number).
2.9.2 Access Lists
Since NetWare networks can have hundreds of fileservers, the network needs a way to reduce the number
of ETS queries, both to reduce network traffic and to prevent long delays in servicing active queues. By
using access lists (created with the Set/Define Protocols NetWare Access command on page 12-59) you
can control which file servers the ETS will and won’t poll for print jobs.
The file servers have no control over the ETS access lists, so they will never know if a misconfiguration of
the access list prevents them from spooling print jobs to the ETS.