Guest User!

You are not Sophos Staff.

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

    Sofrry to keep this going, but evrytine I ping a server it resloves to a different last 2 tuples of an IP address.  Gues what?  Your DNSname resolution services are toast on your inbound routers, or firewall boxes.  

    I wpuld bet that if everyone did this twice a couple fo minutes apart they would get the same problems , it is always the same company's IP's. Do you recognize  LimeLight Networks  in my case

    ping  d2.sophosupd.com

    PING sophos.vo.llnwd.net (208.111.160.6): 56 data bytes

    64 bytes from 208.111.160.6: icmp_seq=0 ttl=50 time=36.742 ms

    64 bytes from 208.111.160.6: icmp_seq=1 ttl=50 time=48.206 ms

    A.R.I.N.  shows me that everytime I ping one of your domain servers it's an IP owned by Limelight Networks.

    (ARIN is American Registry fior Internet Numbers)

    :1020447
Reply
  • 0

    Sofrry to keep this going, but evrytine I ping a server it resloves to a different last 2 tuples of an IP address.  Gues what?  Your DNSname resolution services are toast on your inbound routers, or firewall boxes.  

    I wpuld bet that if everyone did this twice a couple fo minutes apart they would get the same problems , it is always the same company's IP's. Do you recognize  LimeLight Networks  in my case

    ping  d2.sophosupd.com

    PING sophos.vo.llnwd.net (208.111.160.6): 56 data bytes

    64 bytes from 208.111.160.6: icmp_seq=0 ttl=50 time=36.742 ms

    64 bytes from 208.111.160.6: icmp_seq=1 ttl=50 time=48.206 ms

    A.R.I.N.  shows me that everytime I ping one of your domain servers it's an IP owned by Limelight Networks.

    (ARIN is American Registry fior Internet Numbers)

    :1020447
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?