Sophos Anti-Virus for Windows 2000+: log errors generated when you have multiple IPs on the same computer

  • Article ID: 46313
  • Rating:
  • 3 customers rated this article 5.7 out of 6
  • Updated: 08 Sep 2015


The following errors may be seen in RMS logs:

The management agent log may report:
7.05.2008 14:39:44 08A0 E CORBA::Exception: Caught CORBA user exception, ID 'IDL:SophosMessaging/Rejected:1.0' ClientConnection::Reconnect()

The message router log may report:
27.05.2008 14:42:05 11F8 E Attempt to get client interface from non-local caller

"This machine may have more IP addresses than are supported"

First seen in
Sophos Anti-Virus for Windows 2000+


These errors can occur if a computer has been configured with more than 62 IP addresses on the same physical interface. As a result, no IOR is created on port 8192 and the Agent is unable to connect.

This error can also mean that another program is listening on port 8194. This can be checked using the netstat command below:

 netstat -nao | find ":8194"

Bloomberg is known to use the port 8194. For instructions on how to change the ports on a managed Sophos client when Bloomberg is installed see article 14497.

What To Do

Do the following on the computer which is showing the errors.

Note: In the various folder paths mentioned below on 64-bit computers the stated path 'C:\Program Files\' should be  changed to 'C:\Program Files (x86)\'.

  1. In Windows Services stop the services:
    • Sophos Message Router
    • Sophos Agent
  2. Change the IIOP 'listening' port for both Sophos Agent and Sophos Router by editing the relevant registry keys.
    NOTE: This should be a static IP address and is represented in the examples below as x.x.x.x. Replace x.x.x.x with the IP address of your server. If you are unsure about which IP to use, the 'natural', non-virtual IP is preferred.

    You should read the warning about editing the registry, then update the following registry keys:
    • HKLM\System\CurrentControlSet\Services\Sophos Message Router\ImagePath

      By default has the value:
      "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBListenEndpoints iiop://:8193/ssl_port=8194

      Update this to contain the IP address of the machine to read:
      "C:\Program Files\Sophos\Remote Management System\RouterNT.exe" -service -name Router -ORBListenEndpoints iiop://x.x.x.x:8193/ssl_port=8194
    • HKLM\System\CurrentControlSet\Services\Sophos Agent\ImagePath

      By default has the value:
      "C:\Program Files\Sophos\Remote Management System\ManagementAgentNT.exe" -service -name Agent

      Update this to contain the IP address of the machine to read:
      "C:\Program Files (x86)\Sophos\Remote Management System\ManagementAgentNT.exe" -service -name Agent -ORBListenEndpoints iiop://
    • HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\ServiceArgs

      By default it reads:
      -ORBListenEndpoints iiop://:8193/ssl_port=8194

      Update this to read:
      -ORBListenEndpoints iiop://x.x.x.x:8193/ssl_port=8194
    • HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Remote Management System\ManagementAgent\ServiceArgs

      By default it is blank. Update this to read:
      -ORBListenEndpoints iiop://x.x.x.x
    • The following key needs to be created:

      HKEY_LOCAL_MACHINE\SOFTWARE\Sophos\Messaging System\Router\
      LocalClientsOnly (DWORD) Value 0 (zero)
  3. Start the Sophos Message Router Service
  4. Start the Sophos Agent Service

The computer should now be manageable in Enterprise Console.

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

Rate this article

Very poor Excellent