Hello,
First post, and a bit of a newbie.
Scenario, we have a SAM agent installed remotely behind a Network Address Translation (NAT) and we are polling the NAT'd address. The TCP connection appears fine as confirmed on firewall/router logs, however, checking the Windows event log where the solarwinds agent is installed, the agent is trying to send its DCOM queries to the NAT'd IP address and failing.
Example
1. SAM server/poller (192.168.0.10) is polling the NAT IP and port (192.168.10.99:17790)
ie. The node has been added to SAM with the NAT'd IP address. The NAT'd IP address is the only available address for this host that SAM can reach.
2. NAT on the router is translating 192.168.10.99 to the internal hosts IP (10.0.0.99)
3. The SAM poller successfully establishes the TCP connection to the remote host (192.168.10.99, but, real IP of 10.0.0.99)
4. For some reason, the SolarWinds agent on the host appears to be trying to communicate to WMI/DCOM on the NAT'd IP, which, is failing and resulting in an "DCOM was unable to communicate with the computer 192.168.10.99).
Question
Is there any way to force the agent to send the DCOM WMI query to the local IP, not the NAT'd (SAM configured) IP address?
Thanks,
John