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

    Hello Deckchair,

    you can check what the client thinks is its management server's address (parent address) using "View Sophos Network Communications Report" and/or viewing the ClientMRInit-timestamp.log. If they don't look like you specified in your mrinit.conf the it probably didn't get applied. If the address is correct then check if there's actually someone listening (using telnet 10.x.x.x 8194 should result in a successful connection). If this works then take a look at the client's Router logs ([...All Users\Application Data|ProgramData]\Sophos\Remote Management System\3\Router\Logs).

    Christian

    :7843
Reply
  • 0

    Hello Deckchair,

    you can check what the client thinks is its management server's address (parent address) using "View Sophos Network Communications Report" and/or viewing the ClientMRInit-timestamp.log. If they don't look like you specified in your mrinit.conf the it probably didn't get applied. If the address is correct then check if there's actually someone listening (using telnet 10.x.x.x 8194 should result in a successful connection). If this works then take a look at the client's Router logs ([...All Users\Application Data|ProgramData]\Sophos\Remote Management System\3\Router\Logs).

    Christian

    :7843
Children
No Data