Hello to all,
I would have a question regarding the ports / domains to open for my sophos intercept x clients to install.
I have already opened the domains found on this thread (https://community.sophos.com/kb/en-us/121936) except for wildcard domains. Unfortunately my firewall doesn't handle this type of object.
Despite open domains, it seems not enough, the client does not download the application.Thanks
Hi Mario Rossi5
Would you please provide more details about the error you are receiving while you are trying to install Intercept X?
I didn't arrive at the installation.
My firewall block the download.
I think that the inserted domains are not enough. Is it possible?
As I said before my firewall doesn't manage wildicard domain.
HI Mario Rossi5
The above article defines all the domains and ports required for installation and communication from the endpoint to Server. I would suggest you check under the logs where it is getting blocked if you have already allowed these ports and domains.
Is the download of the Windows installer from Sophos Central failing or the download of the software via the SophosSetup.exe failing? If SophosSetup.exe, try creating exclusions for the following:dci.sophosupd.netdci.sophosupd.comd1.sophosupd.netd1.sophosupd.comd2.sophosupd.netd2.sophosupd.comd3.sophosupd.netd3.sophosupd.comAlso it might help if you can share with us the contents of the CloudInstaller log located in C:\ProgramData\Sophos\CloudInstaller\logs\
I've already insert those exclusion whithout success.
The problem is not Sophos but the firewall. Seems that the destinations that I've opened is not enough to install Intercept X.
However now I ask to my customer to tell me what he see on "C:\ProgramData\Sophos\CloudInstaller\logs\"
Hi Mario Rossi5
Please check this article and see if it helps. If you try to download and install from other network source is it successful?
Try excluding 'dzr-api-amzn-us-west-2-fa88.api-upe.p.hmr.sophos.com' as well as it looks like that is where the installer is getting caught up in the logs. Make sure there's no HTTPS scanning that's occurring this this site.
my customer tried to launch this command:
via powershell and then the client installed the software
Glad to know that issue has been resolved for you. Feel free to reach out to us for any further concerns.