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

    Thank you, that was very informative. I believe I can trace the behaviour from the info you have given me now. You are right in that the 192. address is not routable from the 10., the client has to use the address 10.a.b.c in this case but the server does not know about that address itself as it gets NAT'd.

    :7897
Reply
  • 0

    Thank you, that was very informative. I believe I can trace the behaviour from the info you have given me now. You are right in that the 192. address is not routable from the 10., the client has to use the address 10.a.b.c in this case but the server does not know about that address itself as it gets NAT'd.

    :7897
Children
No Data