How can we help you today? How can we help you today?
Benethor
Mark R wrote: » All the connections between the server and the agent are outgoing TCP/HTTPS connections from the agent to the server on port 14146. Is that enough for you to set up port forwarding to get it working? I need to be able to manually configure the agent to a network gateway ip address where server would be hosted. That advanced configuration feature used to exist when I refer to the doc of beta version. It seems to be removed in the latest version I downloaded. Can you bring it back? This would probably solve part of the issues. Another thing : It is possible to have multiple agents on VM with the same name that would reside on different environnement (networks). So, simply using a name to identify an agent would not be enough. To be unique, it would need to be a combinaison of the VM name and of the network gateway address. Allow me to illustrate the problem with an example. I have 3 environments in 3 distinct networks: 1. Env-A. Contains SQL Clone Server (internal IP: 172.100.100.10) Network Gateway IP 192.168.250.1 Port Forwarding rule : external -> 172.100.100.10 on port 14146 2. Env-B Contains SQL Clone Agent 1. (VM name: mySQLServerName1; internal IP: 172.100.100.11) Network Gateway IP 192.168.250.2 3. Env-C Contains SQL Clone Agent 2. (VM name: mySQLServerName1; internal IP: 172.100.100.11) Network Gateway IP 192.168.250.3 As you can observe, Env-B and C are identical copies. I can only differentiate it by its network gateway IP. One last thing, the agents in Env-B and C cannot automatically detect the SQL Clone Server since they are on different networks. I need to be able to manually configure the agents to point it to Env-A gateway (192.168.250.1). I hope this help. Thank you for your help. / comments
Mark R wrote: » All the connections between the server and the agent are outgoing TCP/HTTPS connections from the agent to the server on port 14146. Is that enough for you to set up port forward...
0 votes