Hi,
is there a reliable statement for the URL's or IPs needed by the endpoint to make Heartbeat work?
I Need this because in a project there is no default route to the internet, Sophos allowed.
This thread was automatically locked due to age.
Hi,
is there a reliable statement for the URL's or IPs needed by the endpoint to make Heartbeat work?
I Need this because in a project there is no default route to the internet, Sophos allowed.
Hey Mr.Roboto
Here is the KB regarding which domains and ports are required for this communication.
Below is a screen capture of the default web exception on the Sophos XG for Sophos Services.
I hope this helps, please keep me updated.
Regards,
That is correct, those domains listed are used by the endpoint to communicate it's health (and other information) as part of the Heartbeat function.
It is possible to utilize a proxy, take a look at this KB: How to allow Sophos Central Managed Endpoint, UTM Managed Endpoint, and Sophos Home to use proxy server settings
It is possible to utilize a proxy, take a look at this KB: How to allow Sophos Central Managed Endpoint, UTM Managed Endpoint, and Sophos Home to use proxy server settings
I'll try this in lab. In the last try it seems to work only if the following is given:
If the client has no route to the internet and can't resolve the DNS names, it will not work - so in my last try in the lab.
All of the other stuff of the endpoint software runs over the proxy without any issue.
Thanks for sharing that info! Please don't hesitate to reach out to me if your run into any further issues.