9 Basic nShield Connect, RFS and client configuration
or:
a. To enroll the client with nToken authentication, you must first confirm the nToken
authentication key. On the client, open a command line window, and run the command:
ntokenenroll -H
The following is an example of the output:
nToken module #1
nToken ESN: 3138-147F-2D64
nToken key hash: 691be427bb125f387686
38a18bfd2eab75623320
b. Ensure that you write down the hash or have it otherwise available for the next steps.
c. On the nShield Connect, enter the number of the port on which the client is listening and
press the right-hand navigation button. (The default port is 9004.)
The following is an example of the information displayed by the nShield Connect. This
identifies the client by its ESN and displays the reported key hash:
Client nnnnnnnnnn reported the key hash:
691be427bb125f387686
38a18bfd2eab75623320
Is this EXACTLY right?
Yes No
CANCEL FINISH
d. Compare the hash displayed by the nShield Connect with the nToken key hash returned by
ntokenenroll.
e. If there is an exact match, select Yes and then press the right-hand navigation button to
configure the client.
f. The unit displays a message reporting that the client has been configured. Press the right-
hand navigation button again.
See the User Guide for more about modifying or deleting an existing client, configuring multiple
clients, client licenses, configuring an nShield Connect to use a client with configuration files and auto
push, and advanced configuration options.
9.5 Restarting the hardserver
In order to establish any configuration changes you may have entered, you must restart the hardserver
(also called the nfast server).
Page 61
nShield® Connect - Installation Guide
To Next Page