This article provides information regarding proxy support for Sophos Management Communication System (MCS). The information maybe useful if you are experiencing connectivity problems between the manged endpoint and the Sophos servers when a proxy is used.
Applies to the following Sophos product(s) and version(s)
UTM Managed Endpoint (Windows 2000+)
The default configuration of MCS is to use the system proxy settings and automatic proxy discovery. For each established method available a connection will be attempted. The first to respond will be used, this discovery information and logging of server requests can be found in the McsClient log file as detailed in article 119626.
The configuration file defines the usage of the different proxy discovery methods:
- Windows XP/2003: 'C:\Documents and Settings\All Users\Application Data\Sophos\Management Communication System\Endpoint\Config\Config.xml'.
- Windows Vista+: C:\ProgramData\Sophos\Management Communication System\Endpoint\Config\config.xml'.
in the 'McsClient' section, by default the following options are enabled as denoted by a '1':
These settings are described below:
This indicates whether MCS should use the system proxy server. A non-zero value indicates that the system proxy should be used. A zero value indicates that it should not. On Windows Vista and later, the system proxy can be set using the command
netsh winhttp set proxy. On earlier versions of Windows, the command
proxycfg -p can be used.
Note: The system proxy settings are stored in the registry value:
This indicates whether MCS should attempt to discover proxy servers automatically. A non-zero value indicates that proxy servers should be discovered. A zero value indicates that they should not. Proxy servers are discovered automatically by using the Windows proxy auto-discovery protocol (WPAD) to look for a proxy auto-configuration (PAC) file, and interpreting this to determine an appropriate proxy server or servers for the MCS server.