Enterprise Console: Fixing a port conflict between Bloomberg applications and Enterprise Console

  • Article ID: 25780
  • Rating:
  • 7 customers rated this article 2.7 out of 6
  • Updated: 03 Feb 2016

If computers appear in the Enterprise Console as un-managed, and the Windows Event Log shows that the Enterprise Console service is failing to start, it is possible that there is a port conflict between Enterprise Console and a Bloomberg application.

In the past Bloomberg only used port 8194 and this port clashes with Sophos ports.  Now Bloomberg has also reserved port 8195 as a Bloomberg port and so this needs to be changed accordingly (to 8196).

First seen in
Enterprise Console

What to do

During this procedure you need to reprotect clients. If this is potentially problematic an alternative way of managing this for a small amount of clients are described in the section entitled Reprotecting clients which can be found at the end of this article.

  1. On the management server open the registry editor (Start | Run | Type: regedit.exe | Press return).  Before editing the registry read article 10388.
  2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sophos Message Router.
  3. Double click the ImagePath value in the right hand pane and edit the string to change ssl_port value from 8194 to 8196.
    (Note: You only need to change this once on the server.)
  4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router
    • For 64-bit computers - Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sophos\Messaging System\Router
  5. Double click the ServiceArgs value and edit the string to change the ssl port value from 8194 to 8196.
  6. Go to the file mrinit.conf1 in a text editor such as Notepad and change the line:
  7. Copy mrinit.conf (edited in step 6.) to the following three locations:
    1. C:\Program Files\Sophos\Enterprise Console\
      Note: On 64-bit computers - C:\Program Files (x86)\Sophos\Enterprise Console\
    2. C:\Program Files\Sophos\Enterprise Console\SUMInstaller\
      Note: On 64-bit computers - C:\Program Files (x86)\Sophos\Enterprise Console\SUMInstaller\
    3. The folder described below is based on your console version1
  8. On the management server, open Enterprise Console and click Update Managers.
  9. Right click on the SUM server and select Update Now, this will update the associated distribution location.
    (To verify the new mrinit.conf file is now available to the endpoints, open the mrinit.conf file in Notepad located here:
    (2003) C:\Documents and Settings\All Users\Application Data\Sophos\Update Manager\Update Manager\CIDs\S000\SAVSCFXP
    (2008) C:\ProgramData\Sophos\Update Manager\Update Manager\CIDs\S000\SAVSCXP
    Note: The path may vary depending on the update policy assigned to your endpoints.
  10. The client computers must then be reprotected from Enterprise Console.
  11. On the management server, go to Windows Services and stop and start the Sophos Message Router service.
  12. If necessary adjust Windows-Firewall configuration on Windows XP or Windows Vista, if activated It will take between ten minutes and one hour for the workstations to be updated with the new policy. Alternatively force the policy on to one or more machines.
  13. To confirm the change, open a command prompt in Windows and display a list of active connections by running the command:
    netstat -a
  14. Confirm that the server is listening on port 8196.

1The mrinit.conf file is located in the following folder:

  • Enterprise Console 4.x: C:\Program Files\Sophos\Enterprise Console\SUM\
    • Note: On 64-bit computers - C:\Program Files (x86)\Sophos\Enterprise Console\SUM\
  • Enterprise Console 5+ (upgraded from version 4): C:\Program Files\Sophos\Enterprise Console\SUM\
    • Note: On 64-bit computers - C:\Program Files (x86)\Sophos\Enterprise Console\SUM\
  • Enterprise Console 5+ (fresh install): C:\Program Files\Sophos\Update Manager\
    • Note: On 64-bit computers - C:\Program Files (x86)\Sophos\Update Manager\



Reprotecting clients

If this is undesirable the following alternative may be used:

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent