When AGENT installer are generated, it is possible to override "Server hostname" field with your external hostname or IP address. In case certificate is not signed for required hostname (or does not use *), new certificate has to be created, and ERA Server has to be configured to use it. "Host" field of certificate must contain either * (asterix = any hostname will work) or external hostname used by AGENTs to connect. You ERA Server certificate must be signed for external hostname/IP, i.e. Port may be changed in ERA Server configuration. You have to configure your network/firewalls so that port 2222 is accessible from managed machines. Regarding administering computers outside of your network, there are few critical requirements you have to handle (most common issues): Also check timestamp of this log, as it is possible that AGENT is not even running, and log may be outdated. I would recommend to start checking status.html as it will contain connection relevant error. Please follow AGENT connection troubleshooting steps described in documentation. If this does not work with a virtualized machine, I find it difficult that I can achieve it on a computer external to my network. I do not understand, I have on the same ERA server, a virtualized computer with MVware (CentoOS 6.9), install the agent using the certificate provided in the administration panel, but it still does not appear in the ERA administration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |