Activity overview
Latest activity by Squilldude
I'm having the exact same issue with the same setup as you guys. Any update on this?
I find if you reboot the Redgate server it will work for several hours, then start giving the COMException errors on connectivity in the Configuration page. UPDATE: I may have found the problem in our situation. If your setup has the base monitor in another LAN or in a DMZ, dynamic WMI port rule may not work and you may need to set static WMI ports. When I added "ALL" to our Firewall rule, immediately WMI connectivity was re-established. I'm going to try and set the static WMI port on the cluster servers and see if that works. - https://documentation.red-gate.com/display/SM7/Adding+servers+on+a+different+network+from+your+base+monitor UPDATE 2: It seems to be a problem with Fortigate firewalls not passing the WMI traffic through properly. If you create a rule with from RG server to SQL on the Firewall and allow ALL ports/protocols, then everything works without issues. Pretty much the same scenario I was having - https://forum.fortinet.com/tm.aspx?m=65235 / comments
I'm having the exact same issue with the same setup as you guys. Any update on this?
I find if you reboot the Redgate server it will work for several hours, then start giving the COMException error...