SQL Monitor can't connect SQL cluster in DMZ

Boka

Recently we changed one of our stand alone servers in DMZ creating cluster with two nodes. After setup I double checked all rules on both nodes following "Adding servers on a different network from your base monitor". Test is going fine, without error. But adding server produce errors. Even ping fail! Exception message is "The RPC server is unavailable. (Exception from HRESULT: 0x800706BA" 

Any idea how to solve this

Russell D

If its in a DMZ I'm going to assume that you dont have two way trust configured between the domains/machines. In which case, your best option is a basemonitor running in the DMZ. See https://documentation.red-gate.com/sm/configuring-sql-monitor/multiple-base-monitors.

Boka

Hi Russell
This solution mean that we need another server in dmz for SQL Monitor installation plus SQL Server for repository. SQL can be installed on the same machine with Monitor but anyway it is another server to maintain, check periodically,...
We don't have problem with standalone servers in dmz so I expected smooth migration to cluster. Is there any other way?

Russell D

There are a lot of additional requirements for Clusters, so I'm not sure I'd necessarily expect the migration to be smooth. Authentication to the cluster properties of WMI requires packet privacy for example. I've no idea how that works in practice to a DMZ I'm afraid.

An (Exception from HRESULT: 0x800706BA) is usually firewall related, but the errors that come out of RPC are not always helpful.

You might find this a lot easier using the new WinRM connection method https://documentation.red-gate.com/sm/configuring-sql-monitor/adding-servers-to-monitor/adding-servers-on-a-different-network-from-your-base-monitor/wmi-over-winrm as its much easier to get working, but it's not something I've tried.

Just speaking from experience its easier to stick a basemonitor in the DMZ.