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

How to configure the AD Sync Util to use a proxyserver

Hi,

we have a standardproxy that also handels the DNS requests for connections to the internet.
After configuration the AD Sync Utility tries to contact https://cloud.sophos.com but cannot get a DNS resolution for this URL.

I have not found any option to configure a proxyserver inside the utility and it apparently does not use the one set as system default.

Can somebody please give me a hint how to solve the problem ang get the AD Sync working.



This thread was automatically locked due to age.
Parents
  • Hi,

    As it's a .Net application and running Process Explorer reveals that it's the service (C:\Program Files (x86)\Sophos\Cloud\AD Sync\SophosADSyncService.exe) that contacts the internet.  I assume you can just create a .config file, e.g. "SophosADSyncService.exe.config" in the same directory as the exe to configure it. The following content should configure the proxy:

    <configuration>
    <system.net>
    <defaultProxy>
    <proxy
    usesystemdefault="true"
    proxyaddress="http://proxy:8080"
    bypassonlocal="true"
    />
    <bypasslist/>
    </defaultProxy>
    </system.net>
    </configuration>

    as per: https://msdn.microsoft.com/en-us/library/kd3cf2ex(v=vs.110).aspx, adjust as needed.

    I would suggest checking with Support though as this seems a little hacky and an update might blow it away.

    Regards,

    Jak

Reply
  • Hi,

    As it's a .Net application and running Process Explorer reveals that it's the service (C:\Program Files (x86)\Sophos\Cloud\AD Sync\SophosADSyncService.exe) that contacts the internet.  I assume you can just create a .config file, e.g. "SophosADSyncService.exe.config" in the same directory as the exe to configure it. The following content should configure the proxy:

    <configuration>
    <system.net>
    <defaultProxy>
    <proxy
    usesystemdefault="true"
    proxyaddress="http://proxy:8080"
    bypassonlocal="true"
    />
    <bypasslist/>
    </defaultProxy>
    </system.net>
    </configuration>

    as per: https://msdn.microsoft.com/en-us/library/kd3cf2ex(v=vs.110).aspx, adjust as needed.

    I would suggest checking with Support though as this seems a little hacky and an update might blow it away.

    Regards,

    Jak

Children
  • Hi,

    that solved the problem. I didn't even know it was possible to use config files for .Net applications.
    We will use this as a temporary workaround and get back to this when I get a reply from the Sophos support.

     

    Thank you very much for the great workaround!

    Kai