Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1040 views
  • Users 0 members are here
Options
Suggested
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

SEC upgrade from 5.0 to 5.21 - Remote Management Console problems

Howard_Gyton

Hi,

I've just performed the upgrade from 5.0 to 5.21 without a hitch. Everything looks good and clients are connecting. I then upgraded my local copy of the Management Console. When this completed and I went to run it, it stalled for about 30 seconds and then reported an error, as described in http://www.sophos.com/en-us/support/knowledgebase/118513.aspx

I went through all the steps and everything seemed okay, and the copy on the server connected but my local copy didn't.

I checked my silent installation method was correct:

Console64.msi SERVER_COMPUTERNAME=<SERVER NAME> SERVER_PORT=8192

I did some more digging in the console configuration file and noticed that it had changed the default port from 8192 to 80 as part of the upgrade process. When I changed my local config file to 80 it then connected okay.

At no point during the upgrade process did it mention that the port in use was going to change.

:42776


This thread was automatically locked due to age.
  • 0

    HI,

    Port TCP 8192 is used by Remote Managment System (RMS) so that wasn't right for a remote console to use as there would be a conflict, unless you've changed the ports RMS uses but that seems unlikley if you've re-used 8192 for another Sophos product.

    Note: RMS also uses TCP 8193 and TCP 8194.  Although 8193 isn't used it's still listened on.

    Port 80 is the default for for the management server to listen on for remote consoles, patch clients, and for the local console to connect to the management host service as per: http://www.sophos.com/en-us/support/knowledgebase/114182.aspx.

    The port shouldn't have changed during upgrade regardless of what it was before, there is no intelligence in the installer to automatically pick the default port if a port is in use although it will warn.

    Setting the SERVER_PORT property to 8192 for the Console msi is odd as RMS uses that one.  I'm thinking that it's setup.exe that checks if the port is in use.  If you just run the MSI, the check isn't peformed and it carries on regardless.

    Regards

    Jak

    :42780