Forum Discussion
On-Premise Gateway Change Causing Cloud Connection Issues
Hello,
Our model utilizes multiple on-premise data sources via a gateway, as well as a cloud SQL server connection. We recently had to transition to using a new on-premise gateway, and all of the on-premise data sources were mapped accordingly. When going into the 'Gateway and cloud connections' section of the model settings, I remap the datasources under the new gateway and everything is fine. I even created a test dataset that uses all of the on-premise data sources and the cloud SQL server source to test that a scheduled refresh would work and it did.
The issue arises when trying to perform a scheduled refresh with the full (not test) model. I am consistently getting an error stating that the IP address trying to connect to the cloud SQL server datasource is being rejected. When switching back to the old gateway and mappings, it works fine and isn't rejected. Does switching an on-premise gateway also switch the range of IPs used to connect to cloud datasources?
Thank you
2 Replies
Hi anon_analyst ,
Is the new gateway on a different computer than the old gateway? If so, it makes sense that the IP address is different. The IP address comes from the computer that the gateway is installed on. Check the IP address of that machine and enable the connection for the new IP address.
Hi anon_analyst ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster .
Best Regards,
Dengliang Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
