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

Message Routing???

DJ

Hello, This is a bit complicated to explain but here goes.....

We currently have 2 seperate networks on site, a corp network and a public network which are loosely connected for management purposes. We have users that roam between the 2 networks as well as working from home on direct internet connections. 

We want to be able to manage these clients where ever they are. (I understand about setting up message routers etc) 

The only question ive got really is it possible for several different message routers to have the same DNS alais. So for example when im at home I connect to sophos.mydomain.com on 66.15.25.10 over the internet when im on the corp network I connect to sophos.mydomain.com on 10.10.10.1 and when on the public network I connect to sophos.mydomain.com on 192.168.1.1 . 

Would this work and is anyone doing similar?? 

Cheers

Dave J

:4225


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

    Hello Dave,

    I think the basic question is whether RMS (especially the one on the relays) works with an alias. As shown in Using Sophos message relays in a public WAN it is possible to use only the message relay's FQDN which resolves to different addresses on different networks (of course your DNS must be set up accordingly). It should not matter that these are in fact different machines. Of course all "roaming" clients have to use a message relay in all networks.

    From the docs I understand the message relay has to be set up using the appropriate mrinit.conf but I don't know whether ClientMRInit does anything special on a relay - some quick and dirty tests show that a client will act as a message relay when other clients have it configured as parent but ClientMRInit adjust some settings for a relay. From the ClientMRInit log for a relay I see that a check is made (IsThisComputer) and I'm not sure that it will find a match for it's FQDN-alias. I think it's possible that specifying something like ParentRouterAddress="sophos.mydomain.com,SophosMR1" where SophosMR1 is the relay's NetBIOS name will work.

    Please keep us updated

    Christian

    :4236
Reply
  • 0

    Hello Dave,

    I think the basic question is whether RMS (especially the one on the relays) works with an alias. As shown in Using Sophos message relays in a public WAN it is possible to use only the message relay's FQDN which resolves to different addresses on different networks (of course your DNS must be set up accordingly). It should not matter that these are in fact different machines. Of course all "roaming" clients have to use a message relay in all networks.

    From the docs I understand the message relay has to be set up using the appropriate mrinit.conf but I don't know whether ClientMRInit does anything special on a relay - some quick and dirty tests show that a client will act as a message relay when other clients have it configured as parent but ClientMRInit adjust some settings for a relay. From the ClientMRInit log for a relay I see that a check is made (IsThisComputer) and I'm not sure that it will find a match for it's FQDN-alias. I think it's possible that specifying something like ParentRouterAddress="sophos.mydomain.com,SophosMR1" where SophosMR1 is the relay's NetBIOS name will work.

    Please keep us updated

    Christian

    :4236
Children
No Data
Unfiltered HTML