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

2 Separate Networks

t0m

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
  • 0

    Hi,

    You don't have to install SUM on the machine. You could have the SUM on the "main" network push a distribution location to the bridge machine for example. This CID could then be accessed by the clients "on the other side" either through HTTP or UNC depending on how you shared it out.

    Essentially if you can only pull to a location you need SUM as a child, otherwise you can push to itI suppose.

    The rough process would be as follows if you were installing another SUM on the bridge to be a distribution point and RMS message relay:

    Install SUM from the install share.

    The SUM will shortly be managed in SEC.
    Configure the new SUM in SEC and create a CID from the new SUM for the packages you require.

    Edit the CID(s) to make it a relay CID, where the SUM machine is the relay address.  See mentioned KBA.

    Protect the SUM machine from the edited CID, this will convert it into a relay and install SAV.

    Protect the clients on the other side from the new relay CID.

    All the clients will then be pointing to the relay/child SUM for updated and messaing.  Checking their "ParentAddress" value in the registry will confirm this.

    Hope that helps.

    Regards,
    Jak

    :13051
Reply
  • 0

    Hi,

    You don't have to install SUM on the machine. You could have the SUM on the "main" network push a distribution location to the bridge machine for example. This CID could then be accessed by the clients "on the other side" either through HTTP or UNC depending on how you shared it out.

    Essentially if you can only pull to a location you need SUM as a child, otherwise you can push to itI suppose.

    The rough process would be as follows if you were installing another SUM on the bridge to be a distribution point and RMS message relay:

    Install SUM from the install share.

    The SUM will shortly be managed in SEC.
    Configure the new SUM in SEC and create a CID from the new SUM for the packages you require.

    Edit the CID(s) to make it a relay CID, where the SUM machine is the relay address.  See mentioned KBA.

    Protect the SUM machine from the edited CID, this will convert it into a relay and install SAV.

    Protect the clients on the other side from the new relay CID.

    All the clients will then be pointing to the relay/child SUM for updated and messaing.  Checking their "ParentAddress" value in the registry will confirm this.

    Hope that helps.

    Regards,
    Jak

    :13051
Children
No Data
Unfiltered HTML