Guest User!

You are not Sophos Staff.

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

Failed To Download Update / Could not contact primary server

This morning, the Sophos icon displayed an X in the center of the shield but wasn't grayed out, and the first entry on the menu was a grayed out "Failed To Download Update".  Choosing "Update Now" causes the Sophos AutoUpdate Status window to open, briefly display the "downloading" bar, then end with "Could not contact primary server" and "Authentication Error" followed by the date and time.  Looking into the console, I see that early this morning there were a number of messages regarding Sophos, almost all of them along the following lines: "3/19/15 7:28:22.685 AM SophosSXLD[137]: [SMESXLInterface.m:437] no DNS addresses found", and similar messages appear to go back to at least March 13.

Is there a problem with the Sophos server, and if so what's the prognosis?  Or is it something with my computer, and if so what should I do?  I'm running Sophos Home Edition 9.2.4 (Threat detection engine 3.58.1, Threat data 5.12) on a Mac running OSX 10.9.5.

:1020416


This thread was automatically locked due to age.
Parents
  • Connectivity is not the problem, authentication is.

    $ ping dci.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.70): 56 data bytes
    64 bytes from 68.142.79.70: icmp_seq=0 ttl=57 time=49.153 ms

    $ ping d1.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.69): 56 data bytes
    64 bytes from 68.142.79.69: icmp_seq=0 ttl=57 time=25.462 ms

    $ ping d2.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.69): 56 data bytes
    64 bytes from 68.142.79.69: icmp_seq=0 ttl=57 time=13.116 ms

    com.sophos.autoupdate: Updating catalogue information at 10:31:13 19 March 2015
    com.sophos.autoupdate: Catalogue updated at 10:31:13 19 March 2015
    com.sophos.autoupdate: Error: Failed to get remote version at 10:31:13 19 March 2015
    com.sophos.autoupdate:        Failed to authenticate at 10:31:13 19 March 2015
    com.sophos.autoupdate: Error:    Could not contact primary server at 10:31 on 19 March 2015
    com.sophos.autoupdate:     Access was denied

    :1020455
Reply
  • Connectivity is not the problem, authentication is.

    $ ping dci.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.70): 56 data bytes
    64 bytes from 68.142.79.70: icmp_seq=0 ttl=57 time=49.153 ms

    $ ping d1.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.69): 56 data bytes
    64 bytes from 68.142.79.69: icmp_seq=0 ttl=57 time=25.462 ms

    $ ping d2.sophosupd.com
    PING sophos.vo.llnwd.net (68.142.79.69): 56 data bytes
    64 bytes from 68.142.79.69: icmp_seq=0 ttl=57 time=13.116 ms

    com.sophos.autoupdate: Updating catalogue information at 10:31:13 19 March 2015
    com.sophos.autoupdate: Catalogue updated at 10:31:13 19 March 2015
    com.sophos.autoupdate: Error: Failed to get remote version at 10:31:13 19 March 2015
    com.sophos.autoupdate:        Failed to authenticate at 10:31:13 19 March 2015
    com.sophos.autoupdate: Error:    Could not contact primary server at 10:31 on 19 March 2015
    com.sophos.autoupdate:     Access was denied

    :1020455
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?