Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 27 subscribers
  • Views 1739 views
  • Users 0 members are here
Options
Suggested
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

Security Heartbeat is not working. Any Ideas why?

JanKellermann

Hi,

we want to begin selling XG Firewalls und Intercept X to our customers.

We are trying this features right know and cant get Security Heartbeat working.

We have a XG330 HA Cluster with FullGuard. A Central Account with with Intercept X Advanced for Server with EDR wich is installed on Windows Server 2016 Test Server.

This Server is successfully shown in the Central Console.

The two Firewall are also connectet to the Central Portal

The Agent shows no Error.

But in the XG Dashboard is no Security Hearbeat action at all..... in the Log viewer the Security Hearbeat Log is empty.

The Agent Logs under C:\ProgramData\Sophos\Heartbeat\Logs said:

 2021-02-22T11:13:32.566Z [2492:3964] - ----------------------------------------------------------------------------------------------------
a 2021-02-22T11:13:32.568Z [2492:3964] - Starting Heartbeat version 1.10.1051.0
a 2021-02-22T11:13:32.568Z [2492:3964] - ----------------------------------------------------------------------------------------------------
a 2021-02-22T11:13:32.852Z [2492:4132] - No configuration available to establish Heartbeat connection.

wich is also not very helpful?

Where did this configuration came from?

Can someone help me troubleshoot this?

Regards

Jan



This thread was automatically locked due to age.
Parents
  • +1

    So everything works like a charm now. The mistake was a misconfigured default Policy for Server Protection in Sophos Central. This was used for testing some weeks ago and it was not set back to default, where Security Heartbeat is enabled. I my case it was disabled and for that reason it correctly was not active. :-( After applying the Policy default everthings begin to work magicly!

    Thank you guys for your help!!!

    King Regards

    Jan

Reply
  • +1

    So everything works like a charm now. The mistake was a misconfigured default Policy for Server Protection in Sophos Central. This was used for testing some weeks ago and it was not set back to default, where Security Heartbeat is enabled. I my case it was disabled and for that reason it correctly was not active. :-( After applying the Policy default everthings begin to work magicly!

    Thank you guys for your help!!!

    King Regards

    Jan

Children
No Data