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

Installing Sophos on a PC with Bloomberg and they both run on port 8194

I am deploying Sophos to a PC running Bloomberg installed on it and come to find out Bloomberg runs on the same port as the Sophos Endpoint client. I changed the port in the registry on the client PC like it says to in this link:

http://www.sophos.com/en-us/support/knowledgebase/14497.aspx

The client seems to still work since I can still seem to manage it in the Enterprise Console but I don't understan how I can change the port on the client side but not need to change it one the server side as well. Am I misunderstanding how it works and I should just be happy it seems to be working or do I still have more work on my hands?

:55274


This thread was automatically locked due to age.
  • Hello Tech Tester,

    actually RMS uses a two-way communication. The endpoint first connects to port 8192 on the server (or relay) to obtain an IOR which contains the IP/name and port (usually 8194) to communicate on. When establishing communications the endpoint sends its own IOR and the server uses the IP/name and port (usually 8194) therein to establish a second channel which is used to push policies and commands from SEC to the endpoint.

    BTW - the second channel is not necessary, if it can't be established the client would still receive messages from SEC but only in response to messages from the endpoint (and thus with some latency). Therefore it would - with some limitations - nevertheless work but the router service refuses to start if it finds the designated port in use (it doesn't choose an arbitrary port - even though it could inform SEC the port might be blocked by a firewall).

    Does this answer your question?

    Christian     

    :55289
  • It does, thank you for a very informative response! Just glad to see no further tweaking is required on the server side.

    :55301