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?
Please sign in to leave a comment.