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

RMS client not reporting.

Deckchair

We have remote sites (10.0.0.0)  that cannot report back to the server (192.168.0.0.). The server has a NAT'd address to the 10.0.0.0 network via a firewall and WAN connection. Through the Enterprise Console the client deploys and it collects updates via a UNC path. However the Console remains ignorant of the client status  apparently due to the RMS not being able to talk back. I've found a few articles on setting up DMZ message relays however that isn't our setup and would be difficult to implement. I've tried amending the mrinit.conf to use the 10. address with no success.

Is there anyway to get the client to talk back via RMS or am I missing something?

:7839


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

    Hi,

    I added the NAT'd address from the  WAN as an additional address to the Server. So its primary address is still 192.168.1.x and I added 10.1.1.x aswell. This seemed to make Sophos aware of the 10 subnet and it could respond properly. I'll check when I'm back in the office but I think I had to make some subnet specific settings aswell.

    Yours,

    Steven.

    :12417
Reply
  • 0

    Hi,

    I added the NAT'd address from the  WAN as an additional address to the Server. So its primary address is still 192.168.1.x and I added 10.1.1.x aswell. This seemed to make Sophos aware of the 10 subnet and it could respond properly. I'll check when I'm back in the office but I think I had to make some subnet specific settings aswell.

    Yours,

    Steven.

    :12417
Children
No Data