nCipher firmware upgrade does not use the environment variables for change of default ports.
Originally Published: 2004-09-13
Article Number
Applies To
Issue
ERROR- Server connection failed
\nfast\bin\loadrom
Cause
Resolution
It should not be necessary to remove the environment variables specifying the ports, since they are not used by loadrom.
Hardserver startup settings
You configure the hardserver?s startup settings in the server_startup section of the configuration file.
$NFAST_HOME/kmdata/config, which by default is /opt/nfast/kmdata/config.
A default instance of this file is created when the nCipher support software is installed. This section defines the sockets and ports used by the hardserver. You should need to change this section only if the default ports for privileged or unprivileged connections (9000 and 9001) are not available.
Related Articles
How to determine which firmware version is on an RSA SecurID SID800 authenticator 31Number of Views RSA Authentication Manager Availability of Firmware Updates to Address iDRAC Vulnerabilities 66Number of Views RSA Announces Firmware Update for DS100 Hardware Authenticator 18Number of Views Requests to Customer Support to Assist with Multi-tenant Installations in RSA Web Threat Detection 28Number of Views BIOS firmware update for Dell PowerEdge R210 fails with error 'Cannot use a "-" BIOS in a "-"' 68Number of Views
Trending Articles
RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager Upgrade Process How to delete old or pending certificate signing requests for RSA Authentication Manager console or virtual host replaceme…
Don't see what you're looking for?