Problem:
Why are none of the commands I issue to client machines behind the NAT router actually executing on them but show up as being executed successfully in the LANrev admin console?
Solution:
Beginning with LANrev 4.0 you can now manage client computer behind NAT routers with one exception.
When a command is issued to an agent machine behind a NAT router the command will not go through and will be deferred in the command queue. All the client machines behind the firewall will appear to have the have the same IP address - the public IP of the NAT router. Each time an agent sends in their heartbeat the LANrev server will check if there any commands queued for this agent, keep the connection stream open that the agent used to send in the heartbeat, and use it to send the queued commands back down to the agent.
The one exception where this will not work is if the router doing the NAT is a software router (computer) that also has the agent installed on it. Because it has the public IP address, all commands targeted for agents behind the software router will be received by the agent on this software router machine and be executed there instead of being queued up on the LANrev server. The two solutions for this problem are:
- Don't install the LANrev agent on the software router machine.
- Change the LANrev agent settings on the software router machine to use a different port than all the other client machines behind it.
Date: 7 Feb 2007
Revised: n/a
Components: Agent
Version: 4.0 and higher
