NetWorker: Management Console (NMC) is not accessible on dual-NIC NMC server

The NetWorker Management Console (NMC) server is deployed or upgraded to one of the following versions (or later):

• 19.11.0.4
• 19.12.0.1

The NMC server has multiple Network Adapters. The adapters have different IP addresses, and in some scenarios, different DNS/hostnames associated with the unique IPs.
The NetWorker Runtime Environment (NRE) NMC launcher uses a specific hostname/IP address to connect to the NMC server, for example:

The NMC connection ignores the address specified and connects with another hostname/IP:

The NMC client (host launching the console) does not have network access to the address it is forcing the connection to.
The connection to the NMC fails. 
One, or both of the following symptoms may apply.

• The hostname shown in the "Security Warning" window does not resolve from the host launching the NMC.
• The IP address shown (or associated with the hostname) is not reachable from the host launching the NMC.

This issue appeared due to code change NETWORKER-105298 which resolves a security concern regarding HTTP host header injection. The symptoms outlined appear on NMC servers with multiple Network Adapters. The NMC connection is enforced through the hosts primary address and does not allow connection from another network, such as a management or external address.

The NMC server's gconsole.jnlp file forces the connection to the address associated with the NMC server gstd daemon.

• Linux: /opt/lgtonmc/web/gconsole.jnlp
• Windows (Default): C:\Program Files\EMC NetWorker\Management\GST\web\gconsole.jnlp

<jnlp
        spec="1.0+"
        codebase="https://IPADDR_REPLACE_AT_RUNTIME(192.168.9.100):9000/"
        href="gconsole.jnlp">
        <resources arch="amd64">
...
<application-desc main-class="COM.legato.gwt.framework.LMainWindow">
                <argument>-g</argument>
                <argument>IPADDR_REPLACE_AT_RUNTIME(192.168.9.100)</argument>

The address forced upon launching the NMC is not accessible from the host launching the NMC.

This issue has been raised to NetWorker engineering.

Workaround:

1. On the NMC server, open the gconsole.jnlp with a text editor. Use sudo or root shell on Linux hosts.

• • Linux: /opt/lgtonmc/web/gconsole.jnlp
  • Windows (Default): C:\Program Files\EMC NetWorker\Management\GST\web\gconsole.jnlp

2. Modify the file to force the connection through an address that is reachable from all hosts launching the NMC. For example:

Change:

<jnlp
        spec="1.0+"
        codebase="https://IPADDR_REPLACE_AT_RUNTIME(192.168.9.100):9000/"
        href="gconsole.jnlp">
        <resources arch="amd64">
...
<application-desc main-class="COM.legato.gwt.framework.LMainWindow">
                <argument>-g</argument>
                <argument>IPADDR_REPLACE_AT_RUNTIME(192.168.9.100)</argument>

<jnlp
        spec="1.0+"
        codebase="https://192.168.7.100:9000/"
        href="gconsole.jnlp">
        <resources arch="amd64">
...
<application-desc main-class="COM.legato.gwt.framework.LMainWindow">
                <argument>-g</argument>
                <argument>192.168.7.100</argument>

3. If you are using the NetWorker Runtime Environment (NRE) to launch the NMC, delete the gconsole.jnlp from the Temp folder on the host launching the NMC.

4. Relaunch the NMC.

NetWorker NMC 19.13: Unable to Launch NMC User Interface "No Suitable JVM Found"