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.
  • Peter, 

    sure, but the trace was taken with the client accessing that file, not me directly. I guess the client itself shouldnt get the forbidden code to work, or not? :) 

    :1020501
  • Hi! It's still not working for me. :(

    These are the results I got from pinging and dig:

    ping dci.sophosupd.com

    PING a334.g.akamai.net (111.68.59.48): 56 data bytes

    64 bytes from 111.68.59.48: icmp_seq=0 ttl=60 time=15.789 ms

    ping d1.sophosupd.com

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

    64 bytes from 203.77.188.254: icmp_seq=0 ttl=55 time=74.988 ms

    ping d2.sophosupd.com

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

    64 bytes from 203.77.188.254: icmp_seq=0 ttl=55 time=75.387 ms

    +++

    <<>> DiG 9.8.3-P1 <<>> dci.sophosupd.com

    ;; global options: +cmd

    ;; Got answer:

    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42904

    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:

    ;dci.sophosupd.com. IN A

    ;; ANSWER SECTION:

    dci.sophosupd.com. 32 IN CNAME dci.sophosupd.com.edgesuite.net.

    dci.sophosupd.com.edgesuite.net. 2330 IN CNAME a334.g.akamai.net.

    a334.g.akamai.net. 4 IN A 111.68.59.34

    a334.g.akamai.net. 4 IN A 111.68.59.48

    ;; Query time: 43 msec

    ;; SERVER: 10.0.1.1#53(10.0.1.1)

    +++

    I do not understand what any of these means :(

    I am running Sophos Anti-Virus Home Edition 9.2.2 on OSX Yosemite 10.2.2.

    Please help?

    :1020506
  • I am having these very same issues here in Charlotte, North Carolina and today is Sunday, April 19, 2015!  HELP!!??

    :1020664
  • I just tried a manual update and I got through just fine from Washington DC.  Could it be a problem in your area or with your local machine?

    :1020665
  • I'm still having this or a similar problem.  I'm working from Finland.  Message is 

    MacBook Pro 13

    Sophos version

    Thanks for any help

    :1020689
  • hey txsjohnny and NgunnawalJack

    can you open up terminal, run these commands, and let me know what you get?

    ping dci.sophosupd.com

    ping dc1.sophosupd.com

    ping dc2.sophosupd.com

    dig dig dci.sophosupd.com cname +short

    thanks,

    :1020692
  • Here it is:

    Last login: Fri Apr 24 09:04:06 on console
    john-donovans-macbook-pro:~ johndonovan$ ping dci.sophosupd.com
    PING sophos.vo.llnwd.net (87.248.207.253): 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    Request timeout for icmp_seq 4
    Request timeout for icmp_seq 5
    Request timeout for icmp_seq 6
    Request timeout for icmp_seq 7
    Request timeout for icmp_seq 8
    Request timeout for icmp_seq 9
    Request timeout for icmp_seq 10
    Request timeout for icmp_seq 11
    Request timeout for icmp_seq 12
    Request timeout for icmp_seq 13
    Request timeout for icmp_seq 14
    Request timeout for icmp_seq 15
    Request timeout for icmp_seq 16
    Request timeout for icmp_seq 17
    Request timeout for icmp_seq 18
    Request timeout for icmp_seq 19
    Request timeout for icmp_seq 20
    Request timeout for icmp_seq 21
    Request timeout for icmp_seq 22
    Request timeout for icmp_seq 23
    Request timeout for icmp_seq 24

    ^C
    --- sophos.vo.llnwd.net ping statistics ---
    26 packets transmitted, 0 packets received, 100.0% packet loss
    john-donovans-macbook-pro:~ johndonovan$
    john-donovans-macbook-pro:~ johndonovan$ ping dc1.sophosupd.com
    ping: cannot resolve dc1.sophosupd.com: Unknown host
    john-donovans-macbook-pro:~ johndonovan$ ping dc2.sophosupd.com
    ping: cannot resolve dc2.sophosupd.com: Unknown host

    john-donovans-macbook-pro:~ johndonovan$
    john-donovans-macbook-pro:~ johndonovan$ dig dig dci.sophosupd.com cname +short
    sophos.vo.llnwd.net.
    john-donovans-macbook-pro:~ johndonovan$

    I hope this helps

    Jack

    :1020698
  • hey Jack,

    It looks like you maybe have a firewall blocking ICMP (hence the 100% packet loss) - but the dig comes back with the correct record so we know you're not dealing with a stale DNS issue. 

    I just sent you a PM with a few more commands, feel free to reply to me there when you have a chance!

    :1020717
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?