Sophos Central Endpoint and SEC: Computers fail/hang on boot after the Microsoft Windows April 9, 2019 update. Please follow knowledge base article 133945
Learn about the Benefits of Multi-Factor Authentication (MFA). Turn your MFA on now!
At the end of the Sophos Central endpoint installer, you see an error message that the installation was unsuccessful and that the Internet connection could not be established. The Sophos Endpoint Bootstrap_[Timestamp].txt log shows the return code of 143 and one of the following messages:
Sophos Endpoint Bootstrap_[Timestamp].txt
ERROR,Failed to send a WinHttp request. The error code was 12007 (The server name or address could not be resolved)., ERROR,Failed to send a WinHttp request. The error code was 12029 (A connection with the server could not be established).,ERROR,Failed to connect to the URL https://mcs-amzn-eu-west-19af7.upe.p.hmr.sophos.com/sophos/management/ep.,ERROR,An Internet connection could not be established.,
This article explains the cause of the error 143 and on what to do to resolve it.
The following sections are covered:
Applies to the following Sophos products and versions Central Endpoint Advanced 11.5.11Central Endpoint Standard 11.5.11
SophosSetup.exe is unable to make a successful connection to one or more Sophos URLs.
A successful log shows the following information:
[Date,Time],Information,Checking for internet connectivity..., [Date,Time],Success,Successfully connected to the URL http://dci.sophosupd.com/., [Date,Time],Information,Checking for internet connectivity..., [Date,Time],Success,Successfully connected to the URL https://mcs-amzn-eu-west-1-9af7.upe.p.hmr.sophos.com/sophos/management/ep.,
Note: The Amazon URL may be different depending on the region selected during initial activation of your Sophos Central account.
Ensure that the user account running SophosSetup.exe can access the locations mentioned in the log file.
Note: If SophosSetup.exe is running in the SYSTEM account context, for example, when deploying through Group Policy start-up scripts, ensure that the SYSTEM user account can access the Internet.
If you are using a proxy server, consider the following options:
netsh winhttp set proxy proxy-server="http=your_proxy_server:your_proxy_port;https=your_proxy_server:your_proxy_port"'
netsh winhttp set proxy proxy-server="http=your_proxy_server:your_proxy_port;https=your_proxy_server:your_proxy_port"
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable for us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.