Hello all.
I'm aware that you can use the agent over a 1 to 1 NAT to an external IP. However, that is not what the type of NAT-T support I need. I build VPN tunnels to different locations and policy NAT those remote resources into a subnet of my choice to the datacenter/polling engine location. No matter if the agent is used in active or passive mode it doesn't work for basic polling features. This is because the agent collects the IP address of the server its running on and sends that to the polling engine through a DeviceID/GUID match. However, once the data reaching the polling that resources IP address has now been traversed NAT. This means the agent payload doesn't match the IP as it appears on the polling engine side.
I have been able to get QoE & NetPath working this way. However, the basics information collected after the list resources process won't work once I've updated the polling IP to it's after NAT-T IP. This is a requirement for me as many customers use the local IPv4 space and I can't have overlap on my polling engine side. Hence the reason for using policy NAT in the first place.
I would like a feature on the agent configuration to be able to educate the agent of what IP address it is getting NAT'ed to. This could be an advanced feature that the standard user wouldn't see, as the agent works great for the normal user. Maybe just a little .ini or .xml file I can edit to enable this feature.
If you also would benefit from this feature. Please vote for it with me.
Thanks all.
