A NATed server that runs a receiving Dashboard component (the one that receives incoming connections) has to be identifiable by the same fully qualified DNS name both on the outside and on the inside networks. For example, an internal NATed server mtdashboard-02.mycompany.com resolves to 192.168.x.x on the intranet and to x.x.x.x on the Internet.
The sending Dashboard component (the one that initiates outgoing connections) has to refer to the respective receiving component using that DNS name. For example, Sidecars connecting to the Hub running on the server described above, have to set the hub_hostname parameter to mtdashboard-02.mycompany.com.
The script that installs and/or runs the receiving Dashboard component (these include installhub.bat and hub.bat for the Hub, installsidecar.bat and sidecar.bat for the Sidecar) has to be modified in the following way: the command that invokes the Java virtual machine must have an additional parameter java.rmi.server.hostname set to the fully qualified DNS name.
In the above example, the line beginning with java -Xms64m -Xmx1024m -cp .;hub.jar … in the installhub.bat and hub.bat batch files must be changed to:
java -Xms64m -Xmx1024m -Djava.rmi.server.hostname=mtdashboard 02.mycompany.com -cp .;hub.jar …
Note: The white spaces between parameters have to be observed.