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

2 Separate Networks

We need to set up a second, physically separate network (network B) so that some computers are excluded from the general LAN (network A). These computers require up to date anti-virus so we want to put in a 'bridge' server with two network adapters, one connected to each network.

We don't want an extra place to manage Sophos clients, so is there a way for the computers on network B to talk to our existing EMLibrary server on network A? If we install a second EMLibrary on the bridge server, can it be configured as a 'child' to the existing EMLibrary?

Many thanks in advance!

:12737


This thread was automatically locked due to age.
Parents
  • Hi,

    My first thoughts are "EMLibrary"!. Are you thinking about moving to SEC4.7 with SUM?  

    As for setting up the 2 networks, if you use EML or SUM, the principle is the same.  You can configure either SUM or EML to be a child to a parent SUM/EML. In EML, you publish packages on the parent to make them available to the child SUM, then rather than choosing Sophos as an update location on the child you would choose your parent EML (basically a path to the library share, can be http or UNC).  With SUM you just specify another SUM as the update location.

    You can also configure the machine to be a message relay so all the clients behind this "bridge" report to this server which then relays messages on their behalf to the management server. Article: http://www.sophos.com/support/knowledgebase/article/14635.html has the details on setting up a relay.

    So in this example, the clients would need to be able to access the bridge machine on ports 8192 and 8194 and if you went with http updating port 80.


    Regards,

    Jak

     

    :12751
Reply
  • Hi,

    My first thoughts are "EMLibrary"!. Are you thinking about moving to SEC4.7 with SUM?  

    As for setting up the 2 networks, if you use EML or SUM, the principle is the same.  You can configure either SUM or EML to be a child to a parent SUM/EML. In EML, you publish packages on the parent to make them available to the child SUM, then rather than choosing Sophos as an update location on the child you would choose your parent EML (basically a path to the library share, can be http or UNC).  With SUM you just specify another SUM as the update location.

    You can also configure the machine to be a message relay so all the clients behind this "bridge" report to this server which then relays messages on their behalf to the management server. Article: http://www.sophos.com/support/knowledgebase/article/14635.html has the details on setting up a relay.

    So in this example, the clients would need to be able to access the bridge machine on ports 8192 and 8194 and if you went with http updating port 80.


    Regards,

    Jak

     

    :12751
Children
No Data