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?
This thread was automatically locked due to age.
