Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 92 replies
  • Subscribers 6 subscribers
  • Views 573640 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

Failed To Download Update / Could not contact primary server

cminus

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
  • 0

    Had the same the problem as everyone else with not being able to contact primary server. Running Mavericks 10.9.5 on a 2012 Imac. SAV Home edition 9.2.4. I ran the command that Brian Cook suggested, it appeared to be successful.

    ;; ANSWER SECTION:
    dci.sophosupd.com.    220    IN    CNAME    sophos.vo.llnwd.net.
    sophos.vo.llnwd.net.    12    IN    A    208.111.161.254
    sophos.vo.llnwd.net.    12    IN    A    208.111.160.6

    ;; Query time: 46 msec
    ;; SERVER: 192.168.0.1#53(192.168.0.1)
    ;; WHEN: Thu Mar 19 16:03:09 2015
    ;; MSG SIZE  rcvd: 100

    I registered to post the command, and before posting I tried a manual update and succesfully update my antiivrus defs at 16:13 EDT. So something is working, at least for the time being, at least for me. And it wasn't working early. Just rerun manul SAV update and was successful.

    :1020490
Reply
  • 0

    Had the same the problem as everyone else with not being able to contact primary server. Running Mavericks 10.9.5 on a 2012 Imac. SAV Home edition 9.2.4. I ran the command that Brian Cook suggested, it appeared to be successful.

    ;; ANSWER SECTION:
    dci.sophosupd.com.    220    IN    CNAME    sophos.vo.llnwd.net.
    sophos.vo.llnwd.net.    12    IN    A    208.111.161.254
    sophos.vo.llnwd.net.    12    IN    A    208.111.160.6

    ;; Query time: 46 msec
    ;; SERVER: 192.168.0.1#53(192.168.0.1)
    ;; WHEN: Thu Mar 19 16:03:09 2015
    ;; MSG SIZE  rcvd: 100

    I registered to post the command, and before posting I tried a manual update and succesfully update my antiivrus defs at 16:13 EDT. So something is working, at least for the time being, at least for me. And it wasn't working early. Just rerun manul SAV update and was successful.

    :1020490
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?