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

Intercept X - Ignoring WebProxy Settings for Installation & Updates

Hi Community,

i'am actually facing some webproxy issues with intercept x.
We have a AD infrastructure with a webproxy running in standard mode. The proxy settings are published via AD an internet access is working as expected.

The installation and update of intercept x only workes when i bypass the proxy an grant direct WAN access. But that's not the idea. When i have a look in the UTM logs i can't see any connection coming from the pc using intercept x. So it's useless that i set the exceptions published in some knowledge base articles.

Any hints for me how to force the application to follow the system proxy settings?
I can't find any settings inside of the app to manually set proxy parameters.

Best regards
Patric



This thread was automatically locked due to age.
Parents
  • In a command prompt, if you:

    CD C:\windows\syswow64\

    Note: On 64-bit computers as the SophosUpdate.exe application is 32-bit and will therefore use the WinHTTP config for 32-bit on 64-bit.  If you have 32-bit computers the only netsh will be in the path.

    run:
    netsh winhttp show proxy

    Does this give you expect?

    Otherwise does it help, in the same command prompt to run:
    netsh winhttp import proxy source =ie

    or

    explicitly set it with:
    netsh winhttp set proxy add:port

    Regards,

    Jak

  • Dear Jak,

    you made my day :). I remember a kb-article where i followed these steps without success.
    But today it worked and the client is up to date. Know i can focus on the proxy problem within the AD.

    bigTHX and BR
    Patric

Reply Children
No Data