Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 14 subscribers
  • Views 8589 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

Issues with Sophos Cloud and WSUS managed updates

JamesTredree

Hi,

I'm currently trialling Sophos Cloud enduser protection and am having some issues since installing the software.

On installing, I got an error where the client software could not connect to Sophos so was advised by the KB to configure the following WINHTTP proxy netsh winhttp set proxy proxy-server="http=127.0.0.1:80;https=127.0.0.1:443"

After doing this, the software installed correctly. a couple of days ago, I noticed that the machines which have Sophos installed had stopped getting updates via our internal WSUS server. I checked the configuration and added all of the recommended exemptions for scanning.

I've done some further investigation and identified the WINHTTP settings are causing the issue. The problem I have, when WINHTTP is configured, Sophos updates. Without WINHTTP, WSUS managed updates work. but I can't get them working together.

Has anyone had this issue before? and more importantly, know how to fix it?

Thanks

James



This thread was automatically locked due to age.
Parents
  • 0
    I don't quite understand the concept of running:
    netsh winhttp set proxy proxy-server="http=127.0.0.1:80;https=127.0.0.1:443"
    unless there is a web proxy on the local computer you wish to use but that would be odd to say the least.

    AutoUpdate, MCS and SXL for that matter in the Sophos Cloud endpoint use the WinHTTP library.

    SophosUpdate.exe is a 32-bit process as is MCSClient.exe. Both will use proxy auto detection and will honour any explicit proxy specified in the config of WinHTTP.

    To set up WinHTTP with an explicit proxy you can run the command you mention but for 32-bit processes you need to use netsh from C:\windows\syswow64\. So as an example in a command propt run:
    C:\windows\syswow64\netsh winhttp set proxy proxy-server="http=proxy:80;https=proxy:443"

    I assume you have a proxy?
    How do your clients get configured to use it? pac file, dns, dhcp?

    The only config that doesn't really work with WinHTTP that might work for some browsers is to specify a pac file using a local file.

    References:
    Windows Update client use of WinHTTP
    support.microsoft.com/.../900935

    Netsh command for WinHTTP:
    technet.microsoft.com/.../cc731131(v=ws.10).aspx
Reply
  • 0
    I don't quite understand the concept of running:
    netsh winhttp set proxy proxy-server="http=127.0.0.1:80;https=127.0.0.1:443"
    unless there is a web proxy on the local computer you wish to use but that would be odd to say the least.

    AutoUpdate, MCS and SXL for that matter in the Sophos Cloud endpoint use the WinHTTP library.

    SophosUpdate.exe is a 32-bit process as is MCSClient.exe. Both will use proxy auto detection and will honour any explicit proxy specified in the config of WinHTTP.

    To set up WinHTTP with an explicit proxy you can run the command you mention but for 32-bit processes you need to use netsh from C:\windows\syswow64\. So as an example in a command propt run:
    C:\windows\syswow64\netsh winhttp set proxy proxy-server="http=proxy:80;https=proxy:443"

    I assume you have a proxy?
    How do your clients get configured to use it? pac file, dns, dhcp?

    The only config that doesn't really work with WinHTTP that might work for some browsers is to specify a pac file using a local file.

    References:
    Windows Update client use of WinHTTP
    support.microsoft.com/.../900935

    Netsh command for WinHTTP:
    technet.microsoft.com/.../cc731131(v=ws.10).aspx
Children
No Data
Unfiltered HTML