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

Download of WindowsCloudNextGen failed from server http:∕∕dci.sophosupd.com.

Hello,

I get this error message from all computers running in an office, and also on the server, where I have direct access to;

- I can ping all sophos update locations, directly visiting gives "success" message

- I deleted the auto update Cache, as of
Sophos Endpoint Self Help: Update then reinitiated an update, SophosUpdate.log the contained this:

https://pastebin.com/a0ENj129

 

- directly entering a .dat location in Browser gives a 404

for example:

https://dci.sophosupd.com/v3/d/45/d45972bff24b15b7a3e33f97ca619c39fd84712757a326c22f2c3b0636a17ebc.dat

but I also get  this 404 on my local browser, so it seems the files sophos autoupdate is trying to pull do not exist at all...

 

installed Sophos versions:

https://pastebin.com/5PA8TPNB

Last (successful) Agent Update:
6 months ago


This thread was automatically locked due to age.
Parents
  • Hello  

     

    Any traffic inspection from the update IP/URLs can cause issues with an install/update (due to checksums being altered, holding the update files for too long, etc).
     
    It is not uncommon to see several devices on the same network update correctly and have others fail to update due to a firewall configuration, as each endpoint may be looking to a different IP/URL for its updates.
     
    Your firewall rules need to be checked to include all of the locations listed in this article.

    Please check carefully that the full list of IPs and Domains are white-listed and that no traffic from these locations are being scanned or otherwise held in any way by the firewall or other security appliance. For example, SonicWall or any other Firewall AV would need to have whitelisted Sophos locations/ports mentioned in the linked article above.
     
    These actions can equally affect the update or install process.

  • Hello DianneY,

    if I read the logs correctly all requests fail with a 404 returned from the CDN. Thus either the URL paths that AutoUpdate uses are corrupted, which seems unlikely, or there's some other issue but in any case the firewall can't be blamed - at least IMO. Should these files be publicly accessible or are they pinned to credentials (just asking because I checked what I get back from these URLs and it's a 404 as well).

    Christian

  • Hello  

    Thanks, you're right. Looking at the logs that  sent, the updating credential used (if you search for username in pastebin) do show that the license for it looks to be from an expired eval license (looking at an internal tool we use here), hence the 404 error.

     

      you might need to contact Support for further assistance if you have purchased a license so that a valid updating credential is assigned.

Reply Children