(imported topic written by jonaserlundhammarback91)
Hi
In out production environment we have one deployment network and a lot of different VLAN behind firewalls. These networks also belongs to different customers.
New machines are installed on the deployment network and when they are ready they are moved to correct VLAN and IP address is changed. Deployment net
My problem is that from some of the VLAN’s the BES Client can not connect to the default relays, but they need to connect to a NAT address instead or they need to connect to a local relay already running on the local network.
Currentlly I specify in clientsettings.cfg __RelayServer1, __RelayServer2 and __BESClient_RelaySelect_FailoverRelay. This covers about 95 % of the VLAN’s but still a few there the client can “phone home” when they are moved.
I have tried to use the __BESClient_RelaySelect_TertiaryRelayList setting, but I can not get the clients to try all relays in this list.
The clients only try __RelayServer1, __RelayServer2 and __BESClient_RelaySelect_FailoverRelay and finally they try to connect to the BES Server. The BES Server is behind a firewall and clients are not allowed to connect direct to this machine.
What is the format of __BESClient_RelaySelect_TertiaryRelayList and do I need to do anything more to get it functional?
Is there any other way to tell BES Clients to try more relays? Automatic relay detection will not work, ICMP is blocked from most VLAN’s.
Regards
Jonas