No Management Communication with Sophos Central

Hallo Mr.Roboto,

das Sophos Endpoint Software Forum ist da eine eher schlechte Wahl (wobei die Schuld primär sicher bei Sophos und der Verwendung des Wortes Endpoint liegt). 
da die Clients mit Central sprechen und auch andersherum hört sich nicht wie ein Problem allein auf den Endpoints an, außerdem bedeutet 12152 INVALID_SERVER_RESPONSE The server response cannot be parsed. Ich kann aber nicht sagen, welches der beiden Foren (XG oder Central) das bessere ist.

Christian 

I also notice this behavior when there is no proxy - direct internet access.

Can anybody help?

I also found this in KB:

IMPORTANT [Windows 10 Fall Creators Update, Version 1709 Build 16299: Redstone 3]

Due to changes made to the HTTP Response Codes within this release, Endpoint Self Help will no longer report back the correct Management Communication status. This will be fixed in an upcoming release.

Hi Roboto , 

Are you experiencing the same issue with al your systems and please check the logs from XG , use the command in Shell. 

cat /log/heartbeatd.log 

Also please check the settings on Sophos Central if the XG firewall is synced.

Hi Roboto , 

Are you experiencing the same issue with al your systems and please check the logs from XG , use the command in Shell. 

cat /log/heartbeatd.log 

Also please check the settings on Sophos Central if the XG firewall is synced.

Hi Aditya,

I checked the log but there are only a few INFO events.

Is it a no-go to have a firewall in front of the XG, so there is a double NAT for the clients?  

Hi Roboto ,

Double NAT should not be a problem here, I suspect the packets was parsed through the network or in an adapter and may have caused this issue . I would suggest to check a system through a mobile network and test it.