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
  • I don't think you would have access to that file, more than likely SOPHOS's update service reads that fle and hands off the download parameters to another service.

    If we all had access to that file, we'd all be accessing the file, occasionally at least,  simultaneously which would be a big problemo.  That also means that if you could read or open that file SOPHOS has a GIANT security issue.   It would be like me VPNing into your home forlder and opening up a fiule I thought looked tasty. 

    Probbly not something a security company wouod let happen.

    IMO the best thing to do is, just wait until SOPHOS finds the issue and all will be good again, I suspect that this is effecting more that just is free AV users..

    :1020451
Reply
  • I don't think you would have access to that file, more than likely SOPHOS's update service reads that fle and hands off the download parameters to another service.

    If we all had access to that file, we'd all be accessing the file, occasionally at least,  simultaneously which would be a big problemo.  That also means that if you could read or open that file SOPHOS has a GIANT security issue.   It would be like me VPNing into your home forlder and opening up a fiule I thought looked tasty. 

    Probbly not something a security company wouod let happen.

    IMO the best thing to do is, just wait until SOPHOS finds the issue and all will be good again, I suspect that this is effecting more that just is free AV users..

    :1020451
Children
No Data