We'd love to hear about it! Click here to go to the product suggestion community
Email appliance is having trouble connecting to sea-dynamic.sophos.com
When I tried pinging sea-dynamic.sophos.com the result is:
Pinging sophos.vo.llnwd.net [188.8.131.52] with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out.
I'm currently using 184.108.40.206 as my DNS:
220.127.116.11 <--- this is a network address.
Does anyone here having the same problem as mine?
Have you got into any solutions?
This indicates a network connectivity issue. Do you have an upstream firewall? Make sure that sea-dynamic.sophos.com is not being blocked upstream. You can also run a telnet test to the update server using port 80 to ensure this port is open. Though please take note that changes are taking place to the update mechanism of the email appliance and switching over to HTTPS. The transition is now taking place. For more information regarding this please refer to KBA: Sophos Email Appliance: Upgrade issue with upstream proxy with HTTPS scanning
We're currently having this issue on all 3 of our appliances.They were all able to update at 13:30 today (2017-11-23) Are there any updates with the service currently?
In reply to CEG Infrastructure:
Same problem here.
Impossible retriving updates from 14.30 (UTC+1 Time).
I think Sophos have some problems on their infrastructure.
Please give us an update.
In reply to Davide Sezzi:
the Sophos support says it will detect any anomalies.
This is the second time in 10 days..
we wait for resolution
In reply to Devis Basso:
this is the support response after having contacted it by telephone !!
Good morning,thank you for your report, the problem is well known and development is currently working to identify and resolve the situation, we will be careful notify you of the developments as soon as they are available.Pending further updates can ignore failed update notifications, the problem is not impacting on mail flow, and users can continue to work smoothly.Yours sincerely,
see this KB:
As Devis Basso mentioned already, this is a known issue and is currently under investigation. Follow the KB Article he had linked for updates on the issue.
Thanks for your patience,Karlos