Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 26 replies
  • Subscribers 6 subscribers
  • Views 22693 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

Update not working

fallen1

"Could not contact primary server" message received upon update attempts (both auto & manual) since computer start up 2 Dec 2010.

Auto update preferences panel, even upon unlocking, is grayed out on primary location, user name, password, & use secondary location (which I had left unchecked).

I have had this free Sophos Anti-Virus for Mac about a month.

Mac 10.4.11 on iMac

Thanks for any help.

fallen1

:1001295


This thread was automatically locked due to age.
Parents
  • 0

    Which firewall are you using?  You definitely need access to Akamai servers to get the updates.

    We have been continually investigating failed updates, but the truth is that each case tends to be different, based on network topography.  In the end, it generally comes down to a firewall somewhere blocking access to akamai servers.  Since IPs at akamai are dynamically pooled, and the specific domain/IP used changes based on locale and load, a small static IP whitelist will only apply to a single user for a limited amount of time.

    You could always set a rule that allowed outgoing connections to *.akamaitechnologies.com -- it's generally only established  businesses that use Akamai, and you're dealing with outbound activity.

    :1003845
Reply
  • 0

    Which firewall are you using?  You definitely need access to Akamai servers to get the updates.

    We have been continually investigating failed updates, but the truth is that each case tends to be different, based on network topography.  In the end, it generally comes down to a firewall somewhere blocking access to akamai servers.  Since IPs at akamai are dynamically pooled, and the specific domain/IP used changes based on locale and load, a small static IP whitelist will only apply to a single user for a limited amount of time.

    You could always set a rule that allowed outgoing connections to *.akamaitechnologies.com -- it's generally only established  businesses that use Akamai, and you're dealing with outbound activity.

    :1003845
Children
No Data
Cookie Information Banner