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

Installation fails - DNS issue

Hi All,

Sophos Endpoint is failing to install for our workstations. It fails at the point where it begins to download.

We have found as a workaround that if we change the dns settings on the computer to which the software is being installed, it will download and finish the install successfully. We are changing dns servers to use 8.8.8.8, Google's dns servers. that works for some reason, but our internal DNS servers won't allow the download to finish.

Does anyone know of a true fix for this problem? How do I identify which domains aren't resolving via our own internal dns system? Has anyone else experienced this issue?

This thread was automatically locked due to age.

Parents

0 QC over 6 years ago

Hello ZaneDonaldson,

this is Central? If so, the better forum would be there.

You could check the logs for the actual failing step (BTW - you can then reset DNS to use your internal servers?) and the error encountered. Personally I'd suggest Wireshark as the tool to capture the DNS requests and compare the "internal" and "Google" scenarios.

Christian
Cancel
Vote Up 0 Vote Down

Cancel
0 ZaneDonaldson over 6 years ago in reply to QC

where do I find the installation logs for Endpoint?
Cancel
Vote Up 0 Vote Down

Cancel
0 Nick Cuddemi over 6 years ago in reply to ZaneDonaldson

You can find the logs in C:\Program Data\Sophos

Each component has it's own log file
Cancel
Vote Up 0 Vote Down

Cancel
0 ZaneDonaldson over 6 years ago in reply to Nick Cuddemi

uhhgg, ok...so any advice on which log to check for installation issue as I described?
Cancel
Vote Up 0 Vote Down

Cancel
0 Nick Cuddemi over 6 years ago in reply to ZaneDonaldson

We have a proxy in our enviornment and I noticed that I have to manually set the proxy using netsh in order to get it to install.

cd c:\Windows\SysWOW64

netsh winhttp set proxy proxy-server="http=yourproxy;https=yourproxy"

This was a solution for me, although if you aren't using a proxy this probably won't help, but just in case I wanted to mention it!

I'm not sure which log specifcally, maybe agent or endpoint?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Nick Cuddemi over 6 years ago in reply to ZaneDonaldson

We have a proxy in our enviornment and I noticed that I have to manually set the proxy using netsh in order to get it to install.

cd c:\Windows\SysWOW64

netsh winhttp set proxy proxy-server="http=yourproxy;https=yourproxy"

This was a solution for me, although if you aren't using a proxy this probably won't help, but just in case I wanted to mention it!

I'm not sure which log specifcally, maybe agent or endpoint?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data