Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 5100 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

Doubt with SUM

lazzerini

Hello dear friends,

First of all I need to apologize because my english is not so good.

Here on my company I have many sites and sub-sites with SUM. Example.

I have my main Office called SITEA. I have a branch office called SITEB (with SUM and configured to receive the updates from WEBCID on SITEA) and in some cases I have a sub site called SITEC (with SUM and configured to receive the updates from SITEB).

Everything is working fine, but, all my computer send a connection to your repository source, example, if I have 300 computers on SITEC, I'll have 300 connections to the SITEB. If I have 1500 computers on SITEB I'll have 1500 connections to SITEA. This is a huge problem for me with the persons of Network team (because overload tcp/ip ports connection on my WAN). I know that is possible to configure SOPHOS to consolidate all information on the SUM and send only one TCP/IP connection to the source.

Anyone can help me with this configuration?

:51682


This thread was automatically locked due to age.
Parents
  • 0

    Hello lazzerini,

    with SUM and configured to receive the updates from WEBCID on SITEA

    with that you mean the source for the SUM on SITEB is a HTTP location on SITEA? And the clients get their updates (via UNC or HTTP) from the SUM on SITEB? To make sure - the connections the endpoints make are (mostly) on port 8194? If so, then configuring the SUMs as message relays should solve your problem. For a start please see Enterprise Console: configuring message relay computers.

    300 connections to the SITEB

    this sounds like "something" has been tried but hasn't been correctly implemented. Could you please give some details, whether the connection are UNC/HTTP or only RMS (8194), how the updating policies are configured (e.g. on SITEB the location should.be something like \\SumSITEB\SophosUpdate or http://sum.siteb.com/SophosUpdate) and whether mrinit.conf has been modified (how and where)?

    Christian

    :51688
Reply
  • 0

    Hello lazzerini,

    with SUM and configured to receive the updates from WEBCID on SITEA

    with that you mean the source for the SUM on SITEB is a HTTP location on SITEA? And the clients get their updates (via UNC or HTTP) from the SUM on SITEB? To make sure - the connections the endpoints make are (mostly) on port 8194? If so, then configuring the SUMs as message relays should solve your problem. For a start please see Enterprise Console: configuring message relay computers.

    300 connections to the SITEB

    this sounds like "something" has been tried but hasn't been correctly implemented. Could you please give some details, whether the connection are UNC/HTTP or only RMS (8194), how the updating policies are configured (e.g. on SITEB the location should.be something like \\SumSITEB\SophosUpdate or http://sum.siteb.com/SophosUpdate) and whether mrinit.conf has been modified (how and where)?

    Christian

    :51688
Children
No Data