HP (Hewlett-Packard) HP-UX SNAplus2 Network Card User Manual


 
Chapter 11 277
Managing SNAplus2 Clients
Managing Win16 Clients
To disable the NAP, click on the Windows NAP icon and choose Close. If
any SNAplus2 applications are running, the Close option is not
selectable; if you are sure you want to disable the NAP, stop the relevant
applications before retrying.
Win16 Client Security
SNAplus2 provides a facility for validating the user name and password
of any Win16 client attempting to contact a server running SNAplus2.
This enables you to ensure that only authorized Windows users are able
to access the SNAplus2 system.
By default, Win16 client security is not active, so that any computer with
the Win16 client software installed can access SNAplus2 servers. To
enable Win16 client security, use the following procedure:
Step 1. Agree on a user name and password with each Win16 client user who is
authorized to access the SNAplus2 system.
Step 2. On the Win16 client computer, define this user name. For Windows 3.1 or
Windows for Workgroups 3.11, this name is defined using the snauser
parameter in the [Configuration] section of the sna.ini file,
described in “Win16 Client Initialization File (sna.ini)”.
Step 3. On all servers that this client can access, define this user name and
password to the HP-UX system as a system user name. (The servers the
client can access are specified in the sna.ini file or the Windows
Program Registry.)
Step 4. After enabling the SNAplus2 software on a server, use the following
command:
snapwinsec domain
This command enables Win16 client security on all servers in the
SNAplus2 domain. You do not need to repeat the command when
enabling the SNAplus2 software on other servers.
When a Win16 client starts up and tries to access a server on which
Win16 client security is enabled, the client software displays a pop-up
message requesting a password. This password and the user name from
the sna.ini file are checked against the user names defined to the
HP-UX system on the server. If the Win16 client user does not specify a