Supervising the Network

7-25
Maintaining the NetWare Server
Network Security Features
NOTE: Some combinations of server and client packet signature levels may slow
performance. However, systems with low CPU-demand may not show any
performance degradation. Network supervisors can choose the packet signature level
that meets both their performance needs and their security requirements.
When to Use NCP Packet Signature
NCP packet signature is not required for every installation. Some network
supervisors may choose not to use NCP packet signature because they can
tolerate security risks in the following types of situations:
• Only executable programs reside on the server.
• All network users are known and trusted by the supervisor.
• Data on the NetWare server is not sensitive; loss or corruption of this data would
not affect operations.
NCP packet signature is recommended for security risks such as the
following:
• An untrustworthy user at a workstation on the network
• Easy physical access to the network cabling system
• An unattended, publicly accessible workstation
Server Security
Security is a major concern for administrators and users when working with
files and directories on the network. Several types of security exist in
NetWare Services:
• File system (see “Making the File System Secure and Accessible” in chapter 3).
• NetWare Directory Services (see “Managing the NetWare Directory Services
Tree” in chapter 4).
• Login restrictions (see “Managing the Server” in this chapter).
• Server restrictions (see this section).
Use this procedure to prevent packet forgery, enforce password encryption,
and prevent job servers from creating a window for security breach.
Packet signature is configured with the nwcm utility. The parameters are
listed below.