Hello,
We are getting this message a couple times a week from the content gateway. Our filtering service is installed on a windows server at the same location. So far this message seems to be harmless, where I guess it looses connection but comes right back and I just end up clearing the event as I noticed no issues.
But last week it was together with another message on the content gateway, where it lost connection with the policy broker, and I actually had to reboot the windows server the filtering service was on to get our filtering back. Nothing was being blocked during that time.
The content gateway, filtering service, and policy broker are all on separate servers.
Is this a timeout issue/setting on the content gateway?