How does PDQ Inventory determine what IP address to show?
Some of our workstations show our district's "external" IP address (216.x.x.x) in Inventory instead of their internal LAN (10.x.x.x) addresses. When this happens, custom packages fail to deploy to those workstations.
There are typically 10-15 machines showing the same external IP address in Inventory. The workstations vary.
If I "ping" one of those workstations by AD name from a command prompt, I get a response showing the workstation's internal (10.) IP. If I do a nslookup, I get the internal address.
We do have a number of laptops that switch between wired and wireless networks, so in Inventory I have "Test Multiple Addresses in Name Resolution" checked.
How is Inventory seeing the "external" address? How can I prevent this from happening?
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/
Do those machines have the Agent installed?
Yes. We've blacklisted access to the PDQ agent server and our outside IP no longer appears.
That seems a hammer solution where a screwdriver would be more appropriate. So, what's the screwdriver solution?
Thank you, Mike
Currently all External agents (This is based off of the Agent Status column) will show their external IP by default and all Internal agents show their internal IP by default. This cannot be changed.
If you're experiencing Internal agents with an external IP this is a bug. Please let support know email@example.com. If you're experiencing external agents with an external IP please let support know you have a feature request and explain the reason why you would like that feature and how specifically you would want it to work firstname.lastname@example.org.
Please sign in to leave a comment.