DNS Error on Netpath Probe

David is here from xtrasaas. The NetPath probe has a hard-coded default IP address, which happens to be your router's IP and not the proxy's, causing the DNS problem. If there is a proxy in use, it makes sense that this would be the proxy IP for routing (10.x.x.x). It seems that the version of the software you are working with (2024.2.1) does not allow directing the status step with proxy IP address assignment for the probe. A simple catalyst would be to log onto the proxy through a different web browser. Ensure that the agent is bound to its defunct network interface or set a static route from the routing table. I understand if you don't want to attempt it, but what other options are out there? It would help contact support but it is also likely some limitations are this version.

Davidsk what we observe after few struggles is that even though the laptop is getting added with the VPN / Proxy IP (10.x.x.x) and we are using the same IP to create the probe, but the source IP is still my Router's IP (192.x.x.x) resulting in DNS error, at the NETPATH Probe why is the proxy IP not considered as source IP when that IP is showing as the polling IP. 

Davidsk what we observe after few struggles is that even though the laptop is getting added with the VPN / Proxy IP (10.x.x.x) and we are using the same IP to create the probe, but the source IP is still my Router's IP (192.x.x.x) resulting in DNS error, at the NETPATH Probe why is the proxy IP not considered as source IP when that IP is showing as the polling IP. 

Our case is similar to yours, have you found a solution yet?

got no Solution so far.