This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion
Parents
  • Installed and all our workstation Heartbeats are missing (after rebooting workstations).

    Quite an issue as heartbeats are required for all workstation connectivity. Had to physically connect to the XG to put a temporary access rule in.

  • Seems to be faster, less having to refresh pages to get all inserts.

    No improvements to IPv6.

    Ian

    Added:- still have the heartbeat service failure.

    Probably a bit harsh with the no improvements in IPv6, seeing there is a fix listed.

    The FQDN tab still does not recognise IPv6 addresses, so when will this be fixed?

    Ian

    XG115W - v19 GA - Home

    1225v5 6gb ram, SSID, 4 NICs 20w - v19 EAP - on holiday.

    If a post solves your question please use the 'Verify Answer' button.



    expanded original comment about IPv6.
    [edited by: rfcat_vk at 6:41 AM (GMT -8) on 1 Dec 2021]
  • Also have the heartbeat error. 

    I also get the following message under --> System --> Sophos Central.

    Security Heartbeat is not available due to licenses. Check your licenses. Please contact your Sophos partner to update your Sophos Central or Sophos Firewall licenses.

    The license is okay, though. Re-registering the XG in Central did not help either.

  • If it is indeed a certificate issue, your endpoints need access to the internet and a DNS server to be able to update their certificate. This is the problem for us, because without a heartbeat, our endpoints are blocked on our network, so they can't update the certificate. I have to change our firewall rules so they can get the certificate and then they got there Heartbeats and I could change the firewall rules back.

    Not sure if you have the same sort of setup so I don't know if this will help you resolve your issue.

Reply
  • If it is indeed a certificate issue, your endpoints need access to the internet and a DNS server to be able to update their certificate. This is the problem for us, because without a heartbeat, our endpoints are blocked on our network, so they can't update the certificate. I have to change our firewall rules so they can get the certificate and then they got there Heartbeats and I could change the firewall rules back.

    Not sure if you have the same sort of setup so I don't know if this will help you resolve your issue.

Children
No Data