Of course there can.
For a start, there can because the attribute has NOT been marked as unique in the database, but that's semantics.
How this can happen is usually this scenario:
1 - Computer A has IP 10.10.10.101 - sends inventory, Core records that in the DB.
2 - Computer A is powered off.
3 - Computer A stays powered off long enough for the DHCP lease to expire.
4 - Computer B requests a new DHCP address. Since the lease for 10.10.10.101 expired, it's a valid IP for the DHCP server to hand out.
5 - Computer B gets 10.10.10.101
6 - Computer B sends inventory with this IP-address.
You now have two devices with 10.10.10.101 in the database.
This is not a "fault" of LANDesk - the network information stored in the DB is only as reliable as the information we get in. If clients are offline, there's nothing we can do about it (except show old IP's).
You should NOT be treating the LANDesk stored network info as a "real-time" snapshot of your network. Inventory can not be that, unless you're extremely efficient in sending inventory (and none of your clients ever go offline).
LANDesk EMEA Technical Lead
Deleting this IP address information automatically would also have the negative impact of removing your ability to group machines by the ip subnets. this is a very popular way of identifying locations of machines so it couldn't really be blanked out.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk