Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Agents showing external IP addresses

Michael Elert

November 13, 2018 15:19

My organization has a network segmented across several physical locations. Externally facing IP addresses for each location is different and we are experiencing issues where an asset connected to a different data center, though still internal to our network, is showing up as external and providing the externally facing IP address. This is causing issues with deployments etc.

Is there an easy way around this short of removing the Agent from the asset?

Comments

3 comments

Official comment

Permanently deleted user
September 23, 2019 17:20

We are announcing the End of Life (EOL) of the optional PDQ Agent beta from our existing products. See this blog post for more information https://www.pdq.com/blog/pdq-agent-status-update/
Chris James
November 13, 2018 22:42

This is expected behavior, if the Inventory console that owns this Agent is unable to communicate over Inventory's server port the device will be considered External. If they are connected over a VPN/MPLS, you may want to double check traffic is not being blocked that would prevent the Inventory console from directly communicating with your Agent.

0
Michael Elert
November 13, 2018 22:51

Thanks much. Adjusted the port and now everything is showing as expected.

0