Skip to main content

I am trying to setup my Analysis Models to populate to an on-premises server.   The instructions are telling me :

  • To achieve this scenario, where SQL Server needs to be accessed using the same IP address/FQDN both externally and internally, you can set up Split DNS or a Hosts file entry on the server running the SQL Server instance.

I have tried to edit the host file by adding the external/public IP address as follows.

 

     Internal IP       Exeternal IP or FRQN/Server Name

    172.xx.xx.67    rs-IFS-biServer.domain.com
    172.xx.xx.67    rs-IFS-biServer
    172.xx.xx.67    170.xx.xx.245

 

Am I doing this right or do I have it backwards?

Hi @ballman ,

We have this requirement for the IFS managed cloud customers because the IFS middle tier needs to connect to the on-prem SQL server over the internet. We have only 1 secret that can be configured for SQL server name.

So this single value will be used to establish the connection over the internet as well as internal connections from the SSIS packages. If the public IP address is not resolving internally we will get issues in the SSIS package executions.

After changing the hosts file you can try to connect to the sql server internally through SSMS using the public IP address and see whether it works (try both sql auth mode and windows auth mode). If that is working then the SSIS packages should also work. 

Best regards,

Subash

Reply


Terms & ConditionsCookie settings