NMC: Cannot Connect to Server -- Cannot Authenticate
Summary: The NetWorker Management Console (NMC) is configured with multiple NetWorker servers. Connecting to one or more of the NetWorker servers from the NMC fails "cannot authenticate"
Symptoms
- The NetWorker Management Console (NMC) is configured with multiple NetWorker servers in the NMC Enterprise window.
- One or more of the NetWorker servers fails to connect, reporting "cannot authenticate"
- The connection to the NetWorker server may succeed, but the NMC tabs show no data.
- A connection error appears for the NetWorker server in the NMC "Events" window.
Cause
The NMC is configured to only use one authentication (authc) server. It is not possible to configure the NMC to use multiple authc servers. This issue can appear due to the following:
- The authc host does not have administrative rights on the affected NetWorker servers.
- There is no trust established between the NetWorker server and the NetWorker authc server used by the NMC.
This is expected behavior if the NetWorker server has not been configured to trust the remote authentication server, or the existing trust has expired.
Resolution
From the NetWorker Management Console (NMC) server, determine which NetWorker host is used as the authentication (authc) server. This can be determined in the NMC server's gstd.conf file:
Windows: C:\Program Files\EMC NetWorker\Management\GST\etc\gstd.conf
Example:
{
int http_svc_port = 9000;
int clnt_svc_port = 9001;
int db_svc_port = 5432;
int snmp_trapd_enable = 1;
string module_dir = "/opt/lgtonmc/mod";
list pkg_web_dirmap = {
string alias = "/LGTOnmc";
string path = "/opt/lgtonmc/web";
};
string pkg_jar_files = "/LGTOnmc/java/gst.jar", "/LGTOnmc/java/gwt.jar", "/LGTOnmc/java/gwt_res.jar", "/LGTOnmc/java/comtsk.jar", "/LGTOnmc/java/postgresql-42.5.1.jar", "/LGTOnmc/java/jaxp.jar", "/LGTOnmc/java/jcchart.jar", "/LGTOnmc/java/jcfield.jar", "/LGTOnmc/java/jcpagelayout.jar", "/LGTOnmc/java/forms.jar", "/LGTOnmc/java/looks.jar", "/LGTOnmc/java/antlr.jar", "/LGTOnmc/java/y.jar", "/LGTOnmc/java/ysvg.jar", "/LGTOnmc/java/batik.jar", "/LGTOnmc/java/jide-common.jar", "/LGTOnmc/java/jide-components.jar", "/LGTOnmc/java/jide-dock.jar", "/LGTOnmc/java/ddomain.jar", "/LGTOnmc/java/ddomain_res.jar", "/LGTOnmc/java/json-simple-1.1.1.jar", "/LGTOnmc/java/gconsole.jar", "/LGTOnmc/java/gconsole_res.jar", "/LGTOnmc/java/nwadmin.jar", "/LGTOnmc/java/nwadmin_res.jar", "/LGTOnmc/java/nwadmin_old.jar";
string web_server_user = "nsrnmc";
string web_server_group = "nsrnmc";
string gst_postgres_user = "nsrnmc";
string nsr_nmc_user = "nsrnmc";
string authsvc_hostname = "nsr";
int authsvc_port = 9090;
string current_db_dir = "/nsr/nmc/nmcdb";
};
From the affected NetWorker server, run the following commands from an elevated prompt:
nsrauthtrust -H authsvc_hostname -P 9090 nsraddadmin -H authsvc_hostname -P 9090
After completing this, the connection error for the affected server in NMC Events disappears, allowing the launch of NetWorker Administrator to that server.
Additional Information
NetWorker: How To Enable AUTHC DEBUG for Troubleshooting Purposes
NRE: How to clear Java Cache, enable Java Console and Debugging.