(imported topic written by wolf35991)
I have installed the BES Client onto a Solaris 10 instance, and have configued it to speak to a specific customer Relay Server. However, when I start the agent it ignores my selection, and attempts to speak directly to the top-level Relay Server instead. If I attempt to modify the config file to change the “__Relay_Control_Server1” setting, this is simply changed back to its previous value once I restart the client (even if I update the effective date too).
I had pre-created the /var/opt/BESClient/besclient.config file prior to running the pkgadd command, to install the BES Client.
The besclient.config contained the following entries prior to installation:
EnterpriseClientFolder = /opt/BESClient
StoragePath = /var/opt/BESClient
LibPath = /opt/BESClient/BESLib
value = http://:52311/bfmirror/downloads/
value = 0
I confirmed that the FQHN of the Relay was resolvable by the OS. Incidentally, this is a customer relay server, which is connected to a parent relay server.
I have installed the BES Client onto other Solaris and Linux instances using the above approach, and this was successful. However, it refuses to work on the current host, and I am at a loss to explain it. The log file does not give any indication - it just shows the client attempting to connect to the wrong Relay and failing.
Any suggestions or troubleshooting steps from anyone would be appreciated.