Problem with on-premise gateway

[coneslager]

We have had the gateway working for months, but something has changed.  We have SQL Server on one vm in Azure and the gatewway running on a seperate vm in Azure as well.   The gateway appears to be configured correctly and shows good inside of powerbi, but when I try to map a datasource it fails with the error below.  I have checked firewall logs, sync logs, event view logs, sql server logs, and cant find what is knocking it down.

Unable to connect: The gateway is either offline or could not be reached.Hide details

Activity ID:	3a69ba49-c3c4-449e-9284-050856ee09fc
Request ID:	63fde36f-85f9-6272-087c-6dc72e455f39
Cluster URI:	https://wabi-us-north-central-redirect.analysis.windows.net
Status code:	400
Error Code:	DM_GWPipeline_Client_GatewayUnreachable
Time:	Tue Feb 21 2017 14:44:22 GMT-0600 (Central Standard Time)
Version:	13.0.1700.1204

While this is a seperate isssue, the reason I had to move the gateway of the sql box is , after a pen test, we have to turn of tls1, ssl2,3 and now I cant evein install the gateway.

The on-premises data gateway installer failed to download.
The client and server cannot communicate, because they do not possess a common algorith.

[v-yuezhe-msft]

Hi @coneslager,

Are you able to connect to SQL Server using SSMS installed in the Azure VM that is running gateway? Based on your description, the gateway shows good status, but you get the above error when adding SQL Server data source, right? If that is the case, the issue could be caused by the network between the two Azure VMs, I would recommend you contact your network team to troubleshoot this issue.

In addition, what error message do you get when downloading on-premises data gateway in Azure VM?

Thanks,
Lydia Zhang

[coneslager]

I do have SSMS installed on the same server that the gateway is installed on  and it can connect to the database just fine on the other vm.  This should remove any concerns over networking.

The error message I get on the orignal server, the actual db server, that was running the gateway was at the bottom of the original post. 

The on-premises data gateway installer failed to download install.  (Sorry for the wrong word).
The client and server cannot communicate, because they do not possess a common algorith.  This is after making a few security changes including turning off ssl3, tls 1.0, 1.1.

[v-yuezhe-msft]

Hi @coneslager,

Please ensure that you add all required ports in firewall following the guide in this article, and you install the latest version of gateway on another VM.

Besides, do you use proxy in this sceanrio? Which type of authentication do you use when adding SQL Server data source under gateway?




Thanks,
Lydia Zhang