This article describes how to change the port which Sophos Update Manager (SUM) uses to communicate with the Remote Management System (RMS) agent.
Known to apply to the following Sophos product(s) and version(s)
Sophos Update Manager
What to do
You need to change the SUM configuration file system.xml so SUM uses a different port and create a new configuration file (called scapi_config.txt) so the Sophos Agent service connects to SUM on the same port as entered into the system.xml configuration file.
- Go to Windows services and stop the 'Sophos Agent' and 'Sophos Update Manager' services
- In a text editor open the system.xml file.
- Go to the section headed <SOCKETLISTENER>. In this section is a tag called <PORT>, its value will currently be set to '51234'. Change this value to the port that you would like SUM to communicate over.
- Save your changes.
C:\Program Files\Sophos\Enterprise Console\Remote Management System\ create a file called scapi_config.txt
- Open the scapi_config.txt file, and add the line:
where <PORT> equals the port number that you have already entered in system.xml
- Save your changes.
- Start the 'Sophos Agent' and 'Sophos Update Manager' services.
Note: If you want to reset the SUM and the Sophos Agent to use the default port, repeat steps 1 to 4 above, delete the scapi_config.txt created in step 5 and restart the services described in step 8.
If the port specified in scapi_config.txt does not match the port defined in system.xml the Sophos Agent will fail to connect to SUM and the Agent log file will record the following error in the first few lines (i.e., when the Sophos Agent service starts up):
[DATE] [TIME] 0FDC I SDDM:SCAPI Calling Connect...
[DATE] [TIME] 0FDC I SDDMA: An uninitialized socket was created.
[DATE] [TIME] 0FDC I SDDMA: Failed to connect to the SUM host: connection was refused
[DATE] [TIME] 0FDC I SDDMA: The socket 1224 was shut down.
[DATE] [TIME] 0FDC I SDDMA: The socket 1224 was closed.
[DATE] [TIME] 0FDC E SDDM:SCAPI threw an exception: Failed to connect to the SUM host: connection was refused
Note: Similar errors may be logged for other reasons.
After following the above steps, if the issue still remains, check to see if another third party application is now using the chosen port. Further details can be found in KBA118466