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

Endpoints Not Updating

I am working with Sophos Support to troubleshoot two issues one with web filtering and one with Endpoints not being able to update.

I can ping the update server with no problems:


Pinging sophos-1.hs.llnwd.net [68.142.102.148] with 32 bytes of data:
Reply from 68.142.102.148: bytes=32 time=46ms TTL=57
Reply from 68.142.102.148: bytes=32 time=46ms TTL=57
Reply from 68.142.102.148: bytes=32 time=45ms TTL=57
Reply from 68.142.102.148: bytes=32 time=45ms TTL=57

Ping statistics for 68.142.102.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 45ms

However I have constantly been receiving:

Time: 7/13/2016 16:08:21
Message: AutoUpdate finished
Module: SophosUpdate
Process ID: 4200
Thread ID: 6280

Time: 7/13/2016 16:08:21
Message: Downloading phase completed
Module: Update
Process ID: 4200
Thread ID: 6280

Time: 7/13/2016 16:08:21
Message: ERROR: Download of Endpoint Security and Control failed from server Sophos
Module: Update
Process ID: 4200
Thread ID: 6280

Time: 7/13/2016 16:08:20
Message: Downloading product Endpoint Security and Control from server Sophos
Module: Update
Process ID: 4200
Thread ID: 6280

Time: 7/13/2016 16:08:20
Message: *************** Sophos AutoUpdate started ***************
Module: SophosUpdate
Process ID: 4200
Thread ID: 6280

This was also found in the MCSAgent Log

2016-07-06T16:33:47.184Z [ 6876] INFO  AdapterLogger::Information SAUAdapter - SAU ReportError(107): ERROR: Download of ESHSXP failed from server http://dci.sophosupd.com/cloudupdate

Meanwhile this is from the MCSClient Log and is probably apart of the webfiltering issue:

2016-07-12T01:55:01.033Z [ 8760] WARN  HttpServerImpl::GetAutomaticProxies Failed to get the automatic proxy configuration. The error code was 0.

I have checked how the services are running and what they are logged on as, but still no luck in figuring out why this is still the case after a fresh install with both the full and slim packages.

Has anyone had a similar issue and was able to resolve it?



This thread was automatically locked due to age.